- Created by Pavel Golubnichiy, last modified on Nov 17, 2022
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
- Getting data about operating system
- Getting list of security groups
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 PAM Core to perform service operations on behalf of local resource accounts
Service operations are performed using WinRM. To use local resource accounts as service one, you need to add the resource to the TrustedHosts list of trusted ones on PAM Core server.
Configuring the TrustedHosts list
- Log in to the server on which PAM Core will be installed
- Run Command line (CMD) as Administrator
- Execute the following command:
C:\>winrm s winrm/config/client @{TrustedHosts="Resource1.domain.local, Resource2.domain.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.domain.local, Resource2.domain.local, Resource3.domain.local"}
Service operations in Active Directory
Account for service operations in 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, IPAMADServiceOps
- Fill in the required fields and complete the creation of the account
- Open the context menu of the container, organizational unit, or domain root and select the Properties item
- Go to the Security tab
- Click Add
- Select IPAMADServiceOps account and click Ок
- Click Advanced
- Select IPAMADServiceOps and click Edit
- For the field Applies to: set value Descendant User objects
- In the Permissions: section check Reset password
- Save all changes
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
- Getting data about operating system
- Getting list of security groups
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 Identity 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.
- No labels