Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Конфигурация

Indeed PAM Gateway

The Indeed PAM Gateway необходимо устанавливать на сервер RDSH (component is installed onto Remote Desktop Session Host), который находится в составе Remote Desktop Services на основе сеансов. Если серверов RDSH несколько, то Indeed PAM Gateway должен быть установлен на каждый server. If there are several RDSH servers, then the Indeed PAM Gateway has to be installed onto each of them.

Warning
iconfalse

Все URL-адреса указываются в нижнем регистре.

All URLs are specified in lowercase.

Switch to Перейдите в каталог C:\Program Files\Indeed PAM\Proxy\ProxyApp, откройте для редактирования файл Gateway\ProxyApp folder and edit Pam.Proxy.App.exe.config и заполните секцию file:

<pamProxy ... />:

  • ApiUrl - URL адрес of Indeed PAM Core
  • IdpUrl - URL адрес of Indeed PAM IDPIdP
  • IdpRequiresHttps - требовать HTTPS
  • AgentConnectionTimeout - параметр определяет время в секундах, в течении которого должна быть установлена связь с клиентским компонентом Agent (оставить без изменений)
  • AgentHeartbeatTimeout - параметр определяет время в секундах, в течении которого клиентский компонентом Agent должен отправить Heartbeat (оставить без изменений)

  • FfmpegPath - расположение кодека для обработки видно (оставить без изменений)

  • GatewaySecret - Secret for client keys for additional component authentication

    Note
    iconfalse

    The secret and its hash are generated by the console utility Pam.ConsoleApp.exe (located in \Misc\ConsoleApp folder). Run the command prompt, go to the "ConsoleApp" folder and run the command "Pam.ConsoleApp.exe generate-secret"

    Code Block
    themeRDark
    D:\ConsoleApp>Pam.ConsoleApp.exe generate-secret
    Secret: OClhdGA1M6wWFcYflCfF1qINX8dYbvTrU0Aad4cb7piASoMEEiB2yM0I8N6zq7T/FSQunLyYzsRcm3PhQzqM9w==
    Hash: bQAl17Y58+Htv982eadHmFaDguAPNrjd+Bl9vN0Uw5c=
    Done.



    Warning
    iconfalse

    The hash will need to be specified when setting up Indeed PAM IdP.


  • IdpRequiresHttps - to require secure connection
  • MediaDataStoragePath - адрес сетевого или локального хранилища видеозаписейLeave the rest unchanged

    Code Block
    languagexml
    <pamProxy ApiUrl="https://pam.indeed
.demo:4000
  • -id.local/api" IdpUrl="https://pam.indeed
.demo:4003
  • -id.local/idp" GatewaySecret="OClhdGA1M6wWFcYflCfF1qINX8dYbvTrU0Aad4cb7piASoMEEiB2yM0I8N6zq7T/FSQunLyYzsRcm3PhQzqM9w==" IdpRequiresHttps="true" AgentConnectionTimeout="60" AgentHeartbeatTimeout="20" 
FfmpegPath="ffmpeg.exe" MediaDataStoragePath="\\Storage\Video" />
  • VideoTempPath="C:\ProgramData\Indeed\Pam\VideoTemp\" FileCopyMaxPercentToIgnore="1" FileCopyEnoughPercentToSave="50" FileCopyMinBytesToSave="1048576" />


<appSettings>...</appSettings>

  • Edit the "Culture" value to change the user interface language:

    Code Block
    languagexml
      <appSettings>
        <add key="Culture" value="en" />
      </appSettings>


Configuration of session collection

Warning
iconfalse

Перед создание коллекции необходимо убедиться в том, что на сервер Indeed PAM Gateway не действуют групповые политики, которые выполняют его настройку RDS.

Настройка коллекции

Создайте коллекцию приложений и опубликуйте 
  1. Log in to the server that performs Remote Desktop Connection Broker role and run Server Manager
  2. Switch to Remote Desktop Services - Collections
  3. In the Collections section click Tasks and select the Create session collections item
  4. Create a collection with parameters you need using the wizard
  5. Click Tasks in the RemoteApp Programs section and select Publish RemoteApp Programs item
  6. Click Add, select the
  1. C:\Program Files\Indeed PAM\
Proxy
  1. Gateway\ProxyApp\Pam.Proxy.App.exe
.
  • Откройте Редактирование свойств (Edit Properties) опубликованного приложения, перейдите на вкладку Параметры (Parameters) и установите опцию Разрешить любые параметры командной строки (Allow any command-line parameters).
  • Сохраните все изменения.
    1. application, click Next and then Publish
    2. Open the context menu of the published application in the RemoteApp Programs section and select Edit Properties item
    3. Switch to Parameters, mark the Allow any command-line parameters option and click ОK

    Configuration of access to web applications

    Installation of Indeed-Id ESSO Agent/Admin Pack

    To access web applications through Indeed PAM, you will need to install additional Indeed-Id components:

    • Indeed-Id Admin Pack
    • Indeed-Id ESSO Agent
    • Browser extensions
    Warning
    iconfalse
    • If extension for Google Chrome browser is installed from Google Store, then the Indeed-Id SSO Agent component should be installed using Install1.bat file.

    • If extension for Google Chrome browser is installed via group policies, then the Indeed-Id SSO Agent component should be installed using Install2.bat file.

    Configuring the Internet Explorer extension via group policies

    After Indeed-Id ESSO Agent is installed, the extension is automatically added to Internet Explorer, but it is disabled. To enable and configure extension automatically, proceed as follows:

    1. Run the Group Policy Management snap-in, select the domain, then open the context menu of Group Policy Objects item and click New or use an existing group policy object.
    2. Switch to Group Policy Objects, open the context menu of an object and click Edit
    3. Switch to

      Tip
      iconfalse

      Computer Configuration\Policies\Administrative Templates\Windows Components\Internet Explorer\Security Features\Add-on Management


    4. Open the Add-on List parameter, set the switch to Enabled and click Show in the Options section
    5. Specify the extension ID {D1080A9B-B3D0-443C-AE86-1A2B295A53A2} in the Value name field. Enter 1 in the Value field and save the changes

      Image Added
    6. Switch to

      Tip
      iconfalse

      Computer configuration\Policies\Administrative Templates\Windows Components\Internet Explorer\Internet Control Panel\Security Page


    7. Open the Site to Zone Assignment List parameter, set the switch to Enabled and click Show in the Options section
    8. In the Value name field, enter the URL of the host on which the web application is located, in the Value field enter 2 and save the changes

      Image Added
    9. Switch to

      Tip
      iconfalse

      Computer configuration\Policies\Administrative Templates\Windows Components\Internet Explorer\Internet Control Panel\Advanced Page


    10. Open the Allow third-party browser extensions parameter, set the switch to Enabled and save the changes
    11. Open the Turn on Enhanced Protected Mode parameter, set the switch to Disabled and save the changes
    12. Close the Group Policy Management Editor
    13. Open the context menu of domain or unit, click Link an Existing GPO, select a group policy object and configure it to work with Indeed PAM Gateway server
    14. Log in to Indeed PAM Gateway server and run Server Manager
    15. Switch to Local Server item and open Internet Explorer Enhanced Security Configuration option
    16. Set the switch to Off for Administrators and Users groups

    Configuring the Google Chrome extension via group policies

    Warning
    iconfalse

    Distribution of Google Chrome extension via group policies is only possible if Indeed-Id ESSO Agent is installed with Install2.bat.

    Also, a server with Internet Information Services (IIS) role is required to distribute the extension.

    1. Log in to Internet Information Services (IIS) role server, switch to C:\inetpub\wwwroot\ and create a folder named ChromeExtension
    2. Run Internet Information Services (IIS) Manager and open Sites item in the Connections section
    3. Open the context menu of Default Web Site or any other site and click Add Application
    4. Specify ChromeExtension in the Alias field. Enter C:\initpub\wwwroot\ChromeExtension to Physical path field, then save the changes

      Image Added
    5. Select the site where ChromeExtension application is created,  open MIME Types item in the IIS section, then click Add in the Actions section
    6. Specify .crx in the File name extension field. Specify application/chrome in the MIME Type field and save the changes

      Image Added
    7. Send the URL of ChromeExtension application to support@indeed-id.com

      Note
      iconfalse

      Example: https://server.indeed-id.local/ChromeExtension


    8. Open the C:\initpub\wwwroot\ChromeExtension folder and place the files received from the support service to it:
      • Update.xml
      • icpjelgegalmjjkfoilkbeeodgfbcaam.crx
    9. Install the ADMX templates to domain controller. The templates are included to installation package and located in the IndeedPAM\IESSO\IndeedID.SSO.Agent\Chrome\PolicyTemplates\ADMX
    10. Run the Group Policy Management snap-in, select the domain, then open the context menu of Group Policy Objects item and click New or use an existing group policy object
    11. Switch to Group Policy Objects, open the context menu of an object and click Edit
    12. Switch to

      Tip
      iconfalse

      Computer Configuration/Administrative Templates/Google/Google Chrome/Extensions


    13. Open the Configure the list of force-installed apps and extensions, set the switch to Enabled and click Show in the Options section
    14. Specify the ID of icpjelgegalmjjkfoilkbeeodgfbcaam extension in the Value name field, as well as URL of update.xml file and save the changes

      Image Added

      Note
      iconfalse

      The separator between the application ID and the URL is a semicolon.
      icpjelgegalmjjkfoilkbeeodgfbcaam;https://server.indeed-id.local/ChromeExtension/Update.xml


    15. Open the Configure extension, app, and user script install sources, set the switch to Enabled and click Show in the Options section

    16. Specify the URL of the host In the Value name field where ChromeExtension web application is located and save the changes

      Image Added

      Note
      iconfalse

      The URL must end with an asterisk
      https://server.indeed-id.local/*


    17. Close the Group Policy Management Editor
    18. Open the context menu of domain or unit, click Link an Existing GPO, select a group policy object and configure it to work with Indeed PAM Gateway server

    Backtotop
    Delay0
    Distance250


    Divbox
    classrightFloat

    Table of Contents
    printablefalse