Password Manager Secure Token Server (STS) is installed with Password Manager version 5.10.0. You can configure STS to use internal or external providers with optional Multi-Factor Authentication (MFA).
This feature can only be used on the new Password Manager Self-Service Site to authenticate users in a workflow. It is installed as a service called Password Manager Secure Token Server (STS). It has a configuration and user login interface.
How to use Password Manager STS features
To use the Password Manager STS feature, drag "Authenticate with external provider" activity into any workflow.
-
If you have not set up Secure Token Server connection or did not have valid providers configured in authentication providers, you cannot use this activity.
-
If you set up at least one provider, you can start using it.
-
If you set up more than one, you can select a provider for each activity used in workflows.
Authenticate with external provider on Self Service site
When Authenticate with external provider is the current activity in a workflow, the user is presented with a login form, where they need to provide the credentials for the configured authentication provider. If the configured provider is using MFA, the user will be prompted for the next step. For more information, see Authenticate with external provider.
This login interface uses the browser's language. The supported languages are the following:
-
Argentinean (ar)
-
Chinese (zh)
-
Dutch (nl)
-
English (en)
-
French (fr)
-
German (de)
-
Italian (it)
-
Japanese (ja)
-
Korean (ko)
-
Russian (ru)
-
Spanish (es)
Password Manger STS account restrictions
By default, the Password Manager STS account is set to be the same account as the Password Manager Service Account by the Password Manager installer. The account requires read rights on domain.
Using STS features in a Password Manager realm
The Password Manager STS settings are stored separately from other Password Manager settings in a file on each server. That file will be encrypted using the service user’s DPAPI key by default, or a specified certificate and can be replicated to other servers in a realm. For the replication to work the Password Manager STS instances should use the same ports.
Using Certificate to protect STS configuration
A trusted X.509 certificate with a private key needs to be installed on each server in the LocalMachine’s certificate store. The provided Rsts.exe.config XML configuration file (\One Identity\Password Manager\Service\SecureTokenServer\) will need to be modified on each machine running a PasswordManager STS instance. An example of the XML configuration file is as follows:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<configSections>
<section name="rstsConfigSource" type="Rsts.Config.RstsConfigSource, Rsts"/>
</configSections>
<rstsConfigSource xmlns="urn:Rsts.Config">
<source type="FileConfigProvider">
<fileConfigProvider fileName="rstsConfig.bin">
<protection type="RsaDataProtection">
<rsaDataProtection certificateStore="LocalMachine" certificateLookupType="FindByThumbprint" certificateLookupValue="b23655f8ac0b81c5b00bac0bc0a15e7e1d2b78be"/>
</protection>
</fileConfigProvider>
</source>
</rstsConfigSource>
</configuration>
The thumbprint of the certificate used to encrypt the Password Manager STS settings file is set in the rsaDataProtection element’s certificateLookupValue attribute. Change the value of the certificateLookupValue attribute to match the used certificate’s thumbprint. In case of swapping to certificate encryption, copy the protection element and its child nodes and replace the existing protection element in the masterConfigProvider and slaveConfigProvider node.
NOTE: This configuration will be used after the restart of Password Manager Secure Token Server service.
NOTE: The specified certificate must be valid, trusted and it must exist in the Local Computer’s certificate store. It must have a private key. Access to the private key must be granted to the service account that is running the Password Manager Secure Token Server Windows Service. The private key must be an RSA key, of any length. A certificate with an ECC key is not supported.
|
|
CAUTION: The current rstsConfig.bin will be unusable. For master (or single) instances of STS, reconfiguration has to take place from start. In case of slave instances, if the replication process works correctly, no reconfiguration is needed. |
Pre-configuration steps after swapping between encryption methods on master (or single) instance
Pre-configuration takes place on the PMAdmin site General Settings > Secure Token Server page. Password Manager will check if a reset happened, then try to configure the basic options needed for STS to work properly. If the configuration is successful, no modal should show up. After a page refresh, STS is useable again.
If Password Manager STS settings are not replicated automatically
To replicate the Password Manager STS settings manually, copy the rstsConfig.bin file from the server where you configured Password Manager STS to all other servers. After you copy the file, you must restart the Password Manager STS Windows Service.
NOTE: You can find rstsConfig.bin in <installdir>/One Identity/Password Manager/Service/SecureTokenServer/.
NOTE: This process needs to be repeated every time Password Manager STS settings are modified.
Before the first visit of STS settings, you need to have a binding for your Password Manager site in IIS with the same port that is present in the <Password Manager installation folder>\One Identity\Password Manager\Service\QPM.Service.Host.exe.config under the StsHttpsPort key. By default 20000 is used.
To start using Password Manager STS
-
Open the IIS manager and create an HTTPS binding with this port for Password Manager sites.
-
On the home page of the Administration site, click General Settings > Secure Token Server. The Secure Token Server page is displayed.
-
To change the Password Manager STS settings, if you are prompted to enter RSTS client secret, provide the password. The default password is admin.
The default secret for Password Manager STS is admin. Password Manager will prompt administrators to change the current secret if it is still set to admin. This password will be shared between Password Manager and Password Manager STS instances.
|
|
CAUTION: For security reasons, you must change the password immediately after you have logged in to the configuration interface the first time. |
To change the password, go to Server settings > Administration Password.
To configure the port used by Password Manager STS
-
On the home page of the Administration site, navigate to General Settings > Secure Token Server. The Secure Token Server page is displayed.
-
Click Set SSL. A modal is displayed with Port setting, SSL Certificate setting and Firewall setting.
-
Set the desired port number and set a certificate which will be used for encrypting the communication. The selected certificate will be used only if there are no other settings are set in IIS for that port.
-
(Optional) Administrators can select whether Password Manager should create the firewall rules for the newly selected port.
To set authentication providers
-
On the home page of the Administration site, navigate to General Settings > Secure Token Server. The Secure Token Server page is displayed.
-
Under Add, edit or remove Secure Token Server authentication providers, click Add. A modal is displayed.
-
Select an authentication provider type and its settings will be displayed in the modal. After entering the required settings, you can submit the form to create the authentication provider.
-
The new authentication provider is displayed in the table above the Add button. To create and attach a new 2FA provider to the newly created authentication provider, click Add new 2FA.
To configure STS Server Settings
-
On the home page of the Administration site, navigate to General Settings > Secure Token Server. The Secure Token Server page is displayed.
-
Click Server Settings. A modal is displayed.
-
After you have set the desired settings, click Save.
Provider-specific informations: Duo
In the Duo admin interface you need to create a Web SDK type application to connect with Password Manager STS.
IP range-based rules for hostname resolution
The IP range-based hostname resolution feature allows administrators to define specific IPv4 ranges using IP addresses and subnet masks, and associate hostnames with these ranges.
When a client makes a request to the server, it checks the client's IP address against the predefined ranges. If the client's IP falls within any of the defined ranges, the server responds by providing the corresponding hostname associated with that range to access Secure Token Server (STS).
This feature is particularly useful for network administrators who want to assign custom hostnames or apply specific configurations based on the clients' IP addresses. It enhances security and control by allowing targeted responses based on IP range assignments.
To access this configuration feature on the PMAdmin site, navigate to General Settings > Secure Token Server page.
Using the unregister feature, users registered to the Password Manager can be removed. Note that the user is removed only from the Password Manager and not Active Directory.
To unregister a user from the Password Manager
-
On the home page of the Administration site, click General Settings > Unregister Users.
-
On the Unregister Users page:
-
If you want to unregister individual users, expand the Select Users tree, click Add, manually search for the individual user, select the required user from the results, and click Save.
-
If you want to select a user group, expand the Select Groups tree, click Add, manually search for the individual groups, select the required group from the results, and click Save.
-
If you want to select the entire organization unit (OU), expand the Select Organizational Units tree, click Add, manually search for the individual OU, select the required OU from the results, and click Add.
-
Click Unregister User to unregister the users.
NOTE:
-
To run the task at a specified time, select the Schedule at, specify a time to run the task, and click Save.
-
If a task to unregister an user is scheduled at a later time and you want to unregister the user at the current instance, click Remove Setting to delete the scheduled task settings and click Save.
-
If you have the Domain management account configured with a user other than the Active Directory Administrator then, make sure that the Write permissions are available to the storage attribute of the security questions (comment, by default) for all the users/ groups/OUs that is configured to be unregistered.
-
If the users/ groups/ OUs that needs to be unregistered are a member of Readers/ Administrators group in the ADLDS then, the Write Permissions are already inherited.
Use the Bulk Force Password Reset feature to force selected users, groups and organizational units to change their passwords.
To enforce a password change for users
-
On the home page of the Administration site, click General Settings > Bulk Force Password Reset.
-
On the Bulk Force Password Reset page:
-
If you want to enforce password change for individual users, expand the Select Users tree, click Add, manually search for the individual user, select the required user from the results, and click Save.
-
If you want to enforce password change for a user group, expand the Select Groups tree, click Add, manually search for the individual groups, select the required group from the results, and click Save.
-
If you want to enforce password change for the entire organizational unit (OU), expand the Select Organizational Units tree, click Add, manually search for the individual OU, select the required OU from the results, and click Save.
-
Click Reset Passwords.
NOTE: Consider the following when using the Bulk Force Password Reset feature:
-
Password reset is achieved by setting the Users must change password at next logon flag of the selected user(s) to true. This flag cannot be set to true, if the Password never expires flag is also true.
-
If you have the Domain management account configured with a user other than the Active Directory Administrator, make sure that write permissions are given to the pwdlastset attribute.
