- Created by Maksim Kuzmov, last modified by Pavel Golubnichiy on Jan 24, 2020
User directory
Active Directory organizational units or containers are used as user directory. A service account is required to work with directory, in order to read directory users properties.
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. All Active Directory domain users have a right to read the properties of other users by default.
Video storage
Video storage is a network folder with configured access. A service account is required to access video storage. To access the video store you need a service account to perform read and write operations. It is recommended to use the existing IPAMManager account as the service one.
A domain account is required to work with video storage.
To create a network folder, follow these steps:
- Create a folder on the network store.
- Call the contextual menu of the folder you created, select the item Share with > Specific people.
- Enter the username (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 creating a network folder by clicking Share.
Shadow file storage
Files that the user transfers to the target resource are copied to the storage. It is a network folder similar to a video storage.
Data storage
Indeed PAM uses Microsoft SQL Server or PostgreSQL Pro to store data. The following components require databases:
- Indeed PAM Core (DB IPAMCore, DB IPAMTasks)
- Indeed PAM IdP (DB IPAMIdP)
- Indeed Log Server (DB ILS)
The ILS database is required only for a configuration with event storage in the DBMS. When using Windows Event Log, creating a database is not necessary.
Table creation, data read and write operations are performed under service account to use with data storage. The account should have the following database rights:
- db_owner - this is required to create tables upon the first request to database
- db_datareader - for read operations from database
- db_datawriter - for write operations to database
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 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 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, in the Definition tab, enter the new password, in the Privileges tab, in the Can login? item select Yes, click Save
- Go to the created databases, open the context menu, select Properties, specify the Owner as IPAMSQLService
- Go to the Security tab, in Privileges add a new row, in the Grantee column select IPAMSQLService from the list, click on the cell in the Privileges column and select All and With grant option
- Click Save, repeat for the rest of the databases.
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
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 Container or Organization Unit in which the access accounts are located
- Select Properties item
- Go to 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 the changes
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