- Created by Pavel Golubnichiy, last modified on Jul 12, 2020
You are viewing an old version of this page. View the current version.
Compare with Current View Page History
« Previous Version 2 Next »
Active Directory
Indeed PAM interacts with end users through an account that will read directory users and their attributes
Creating an account to use with user directory
- Run the Active Directory Users and Computers snap-in
- Open the context menu of organizational unit or container
- Select Create - User item from the menu
- Specify the user name, say, IPAMManager
- Fill in the mandatory fields and complete the account creation
Alternatively, you can use an existing account.
Creating and configuring the service account to use with Active Directory
- Start the Active Directory Users and Computers snap-in
- Open the context menu of the Container or Organization Unit
- Select Create - User item
- Enter the name, for example IPAMService
- Fill in the required fields and complete the creation of the account
- Open the context menu of the created account and select the Properties item
- Go to the Member Of tab and click Add
- Search for the Domain Admins security group and click Ok
- Save all changes
Or use an already created account.
Membership in the Domain Admins security group is required to reset the password for domain administrators that Indeed PAM should manage. If end users should not receive domain administrator privileges, and Indeed PAM should not manage these accounts, then delegation of rights to reset the password for certain containers or the domain as a whole will be required.
- Run the Active Directory Users and Computers snap-in
- Open the context menu of the Container or Organization Unit
- Select Create - User item
- Enter the name, for example IPAMService
- Fill in the required fields and complete the creation of the account
- Open the context menu of the container, organizational unit, or domain root
- Select the Properties item
- Go to the Security tab
- Click Add
- Select IPAMService account and click Ok
- Click Advanced
- Select IPAMService account and click Edit
- For the field Applies to: set value Descendant User objects
- In the Permissions: section check Reset password
- Save all changes
Storage of media files and shadow copies
File storages are necessary for aggregation and long-term storage of videos, screenshots and files transferred in sessions.
File storage account
It is recommended that you use an already created IPAMManager account. A domain account is required to work with file storage.
Create and configure file storage
- Log in to the server, which will act as a file storage
- Create folders, for example MediaData and ShadowCopy
- Call the contextual menu of the folder you created, select the item Share with > Specific people.
- Enter the username, for example IPAMManager and click Add.
- In the "Permission level" column, click the Read value next to the IPAMManager user and select Read/Write from the menu.
- Finish by clicking Share.
Data storage
Indeed PAM uses Microsoft SQL Server or PostgreSQL Pro to store data. The following components require databases:
- IPAMCore - Indeed PAM Core component database is used to store Indeed PAM privileged accounts, resources, permissions, and other service data
- IPAMTasks - The Indeed PAM Core component database is used to store scheduled tasks
- IPAMIDP - Indeed PAM IdP component database is used to store authenticators of Indeed PAM users and administrators
- ILS - The Indeed Log Server component database is used to store the Indeed PAM event
Database creation
Microsoft SQL Server
- Run Microsoft SQL Management Studio (SSMS) and connect to Microsoft SQL Server instance
- Open the context menu of Databases item
- Select the New Database item
- Specify a database name, for example IPAMCore, IPAMTasks, IPAMIdP, ILS
- Click ОK
PostgreSQL, PostgreSQL Pro
- Launch pgAdmin and connect to the PostgreSQL Pro server
- Open the context menu of the Databases item
- Select Create, Database
- Specify a database name, for example: IPAMCore, IPAMTasks, IPAMIdP, ILS
- Click Save
Creating a service account to work with data storage
Microsoft SQL Server
- Start Microsoft SQL Management Studio (SSMS) and connect to the Microsoft SQL Server instance
- Expand the Security item
- Open the context menu of Logins item
- Select the Create login item
- Enter the name, for example IPAMSQLService
- Select SQL Server authentication item and fill in the required fields
- Switch to User Mapping item
- Check IPAMCore, IPAMTasks, IPAMIdP and ILS databases
- Check database roles db_owner, db_datareader and db_datawriter
- Click ОK
PostgreSQL, PostgreSQL Pro
- Launch pgAdmin and connect to the PostgreSQL Pro server
- Open the context menu of the Login/Group Roles item
- Select Create, Login/Group Role
- Specify a Name, for example IPAMSQLService
- Go to Definition tab, enter the new password for account
- Go to Privileges tab, check Yes for Can Login? and Superuser? items
- Click Save, repeat for the rest of the databases.
The rights db_owner for Microsoft SQL Server and Superuser for PostgreSQL are required only for the first access to the database.
IIS
The WEB Server role can be installed using the Powershell script located in the distribution folder \Misc\IISSetup. The script checks for IIS components and installs them if necessary.
Additional components Microsoft .NET Core 3.1 Hosting Bundle and URL Rewrite (from the MSComponents.zip archive) should be installed only after IIS.
Secret Generation for Applications
For Indeed PAM Core, Indeed PAM Gateway, SSH Proxy and ConsoleApp to interact with Indeed PAM IdP, you need to generate a key and its hash.
- Go to Indeed.PAM_2.2.0\Misc\ConsoleApp folder
- Edit file appsettings.json
- Enter https://1 as a value for the parameter apiUrl
- Enter https://2 as a value for the parameter idpUrl
- Run Command prompt (CMD)
- Run the Pam.ConsoleApp.exe utility with the generate-secret parameter
- Save the secret and its hash
Service operations on Active Directory
Active Directory service operations are performed on behalf of the service account:
- Checking the connection to the Domain
- Domain accounts synchronization
- Checking the domain account password
- Changing the domain account password
Create a security group for Active Directory Privileged access accounts
- Start the Active Directory Users and Computers snap-in.
- Open the context menu of the Domain, Container or Organization Unit
- Select Create - Group item
- Enter the name, for example IPAMPrivilegedAccounts
- Select Global in the Group scope section
- Select Security in the Group type section
- Save the changes
Service operations for Windows resources
The following service operations are performed at Windows resources on behalf of the domain or local service account:
- Checking of connection to resources
- Synchronization of local accounts
- Checking of local account passwords
- Changing of local account passwords
Configuring a domain account as service one
- Log in to resource
- Run the Computer management snap-in
- Switch to System tools - Local Users and Groups - Groups section
- Open the context menu of Administrators group
- Select Properties item
- Click Add
- Select the domain account to be used as service one for the resource and click OK
Configuring a local account as service one
If you plan to use local built-in administrator account as service account, then no additional configuration is required. Otherwise, proceed as follows:
- Log in to resource
- Run the Computer management snap-in
- Switch to System tools - Local Users and Groups - Groups section
- Open the context menu of Administrators group
- Select Properties item
- Click Add
- Select the local account to be used as service one for the resource and click Ок
- Run Windows registry editor (RegEdit)
- Expand the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ branch
- Open the context menu of System section
- Select Create - DWORD (32-bit) Value
- Specify the parameter name - LocalAccountTokenFilterPolicy
- Open the context menu of LocalAccountTokenFilterPolicy parameter
- Select Modify item and set the Value data: equal to 1
Registry editing is required due to restrictions on remote WinRM management for all local accounts except for built-in administrator account.
Configuring a resource to use local accounts as service one
Synchronize accounts operation is performed using remote WinRM management. It is necessary to add the resource to the TrustedHosts list if local resource accounts are used as service ones.
Configuring the TrustedHosts list
- Log in to the server on which Indeed PAM Core will be installed
- Run Command line (CMD) as Administrator
- Execute the following command:
winrm s winrm/config/client @{TrustedHosts="Resource1.demo.local, Resource2.demo.local, Resource3.demo.local"}
The specified resources shall be added to the TrustedHosts list.
When adding new resources to the trusted list, you must specify previously added resources and new ones, since the new value overwrites the old one.
@{TrustedHosts="Resource1.demo.local, Resource2.demo.local, Resource3.demo.local, NewResource.demo.local"}
Service operations for *nix resources
The following service operations are performed at *nix resources on behalf of the local service account:
- Checking of connection to resource
- Searching for local accounts
- Checking of local account passwords
- Changing of local account passwords
Creating and configuring a service account
- Log in to resource.
- Run Terminal.
Create a user, for example IPAMService:
adduser IPAMService
Add the user to SUDO group
usermod -aG sudo IPAMService
Configuring a group of privileged accounts
Automatic searching and adding of Access accounts to Indeed PAM is performed based on their permission to execute a SUDO command. To grant the permission to execute SUDO command, you need to edit the /etc/sudoers file.
SSL Configuration for Indeed PAM components
Secure interaction will require certificates for servers that have Indeed PAM components installed. The certificates can be generated using the standard Machine template.
- No labels