Get Live Help
The following describes how to use SPS with One Identity Starling and take advantage of companion features from Starling products such as 2FA and Identity Analytics.
An existing Starling organization (tenant)
NOTE: Consider the following:
If you have several Starling organizations, you can join your SPS to any of the existing organizations, however, ensure that you remember the Starling organization you joined to your SPS. This might be required if there is a join failure and you need to unjoin SPS from the respective Starling organization.
To use Starling with SPS, you need a Starling organization and account within the United States data center (European Union data center is not yet supported).
To join SPS to One Identity Starling
Navigate to Basic Settings > Starling Integration.
CAUTION: If SPS nodes are joined to a cluster, ensure that you initiate your Starling integration on the Central Management node.
To check the availability of SPS and Starling, that is, SPS can connect directly to the web and SPS can access Starling, click Check availability.
If your SPS cannot connect directly to the web, check your Internet connection and ensure that SPS can connect to the web, then re-initiate the process of joining your SPS to Starling.
If your SPS is behind a web proxy, navigate to Basic Settings > Network > HTTPS Proxy and configure the proxy settings. For more information, see Network settings.
Currently only built-in Certificate Authorities are supported. If web proxy replaces the certificates of the Starling website on-the-fly, the join process might fail.
If SPS cannot access Starling, wait until Starling is available and re-initiate the process of joining your SPS to Starling.
Figure 81: Basic Settings > Starling Integration — SPS is ready to join Starling
When SPS is ready to join Starling, click Start join.
NOTE: Once you click Start join, you cannot stop the process and your SPS machine will be joined to Starling.
Ensure that you continue with the join process, and once the join process is complete, if required, you can unjoin SPS from Starling.
For more information, see Unjoining SPS from One Identity Starling.
The One Identity Starling site will open in a new tab.
To allow SPS to access your Starling organization and the services that you have subscribed to, click Allow.
The Join to Starling screen is displayed.
Copy your Credential String from the page.
The credential string allows SPS to communicate with Starling.
Navigate back to the SPS tab.
Paste your credential string into the Credential string field.
NOTE: If for some reason you cannot paste the credential string, you can re-retrieve it by refreshing this page and repeating the join process. You will receive the same credential string if you did not change your host name.
To complete the join process, click Save & finish joining.
Your SPS instance is joined to Starling.
Figure 82: Basic Settings > Starling Integration — Example of SPS joined to Starling
If you intend to decommission an SPS machine, or replace it with another one, you have to unjoin that machine and join the new machine. The following describes how to unjoin SPS from One Identity Starling.
existing Starling organization (tenant)
A SPS that is already joined to One Identity Starling.
To avoid errors, SPS now prevents you to unjoin SPS from One Identity Starling if Remote Access is enabled. You can only unjoin SPS from One Identity Starling if you first disable Remote Access.
To unjoin SPS from One Identity Starling
The Users & Access Control menu (previously named AAA menu) allows you to control the authentication, authorization, and accounting settings of the users accessing One Identity Safeguard for Privileged Sessions (SPS). The following will be discussed in the next sections:
For details on how to authenticate locally on SPS — see Managing One Identity Safeguard for Privileged Sessions (SPS) users locally.
For details on how to authenticate users using an external LDAP (for example Microsoft Active Directory) database, see Managing One Identity Safeguard for Privileged Sessions (SPS) users from an LDAP database.
For details on how to authenticate users using an external RADIUS server, see Authenticating users to a RADIUS server.
For details on how to control the privileges of users and usergroups, see Managing user rights and usergroups.
For details on how to display the history of changes of SPS configuration, see Listing and searching configuration changes.
By default, One Identity Safeguard for Privileged Sessions (SPS) users are managed locally on SPS. In order to add local users in SPS, all steps of the following procedure need to be completed:
For detailed instructions on how to create local users, see Creating local users in One Identity Safeguard for Privileged Sessions (SPS).
Assign users to groups.
For details about how to add a usergroup, see Managing local user groups.
Assign privileges to groups.
For information on how to control the privileges of usergroups, see Managing user rights and usergroups.