One Identity Safeguard for Privileged Passwords 2.9 - Administration Guide

User locked out

If a user has not logged onto Safeguard for Privileged Passwords for a set number of days, Safeguard for Privileged Passwords disables the user account.

User not notified

If a user did not receive an email notification, first check to see if you have set everything up in Safeguard for Privileged Passwords correctly for the email notifications to work properly. For more information, see Enabling email notifications.

Notification lists

Safeguard for Privileged Passwords does not dynamically maintain the email addresses for an escalation notification contact list.

If you change a Safeguard for Privileged Passwords user's email address or delete a Safeguard for Privileged Passwords user after creating a policy, you must update the email addresses in escalation notification contact lists manually. For example, when you create a policy you can indicate who to contact when emergency access has been used. If a user has changed his or her email address, the notification will not be received by that individual. Furthermore, if a user has been deleted from Safeguard for Privileged Passwords, he or she will still receive the notification.

Frequently asked questions

The following topics will help you find answers to some of your questions about managing Safeguard for Privileged Passwords:

How do I access the API

You can use the API to automate Safeguard for Privileged Passwords tasks and access functionality not currently available in the Windows desktop client. Safeguard for Privileged Passwords has the following API categories:

• Appliance: Resources used to manage the appliance itself (like setting the time, network configuration, syslog, etc.)

  https://<Appliance IP>/service/appliance/swagger/

• Core: Resources used to govern policy and manage accounts, etc.

  https://<Appliance IP>/service/core/swagger/

• Notification: Resources used to query the Safeguard for Privileged Passwords Appliance status

  https://<Appliance IP>/service/notification/swagger/

You must use a bearer token to access most resources in the API. When using the Swagger web UI (as referenced in the URLs above), click the Authorize button at the top of each page and log in using the web UI. The Swagger web UI adds the bearer token to each API request automatically. However, if you are manually making the API request or writing your own application/script, perform the following two steps to obtain a bearer token.

1. You must first authenticate using the OAuth 2.0 Resource Owner Password Credentials or Client Credentials grant types. An example of the former is:

   POST https://<ApplianceIP>/RSTS/oauth2/token

   Host: <ApplianceIP>

   Content-Type: application/json

   Accept: application/json

    

   {

   "grant_type": "password",

   "username": "<Username>",

   "password": "<Password>",

   "scope": "rsts:sts:primaryproviderid:local"

   }

   Where:

   • grant_type is required and must be set to password.
   • username is required and set to the user account you want to log in as.
   • password is required and set to the password associated with the username.

   • scope is required and set to one of the available identity provider's scope ID. The value shown in the example request, "rsts:sts:primaryproviderid:local", is the default value available on all Safeguard for Privileged Passwords Appliances. User accounts that you create in Safeguard for Privileged Passwords directly (that is, not an Active Directory or LDAP account) will most likely have this scope value.

     NOTE: The list of identity providers is dynamic and their associated scope ID can only be obtained by making a request to: https://<ApplianceIP>/service/core/v2/AuthenticationProviders and parsing the returned JSON for the RstsProviderScope property.

   If you wish to authenticate using a client certificate, you must use the OAuth 2.0 Client Credentials grant type in which your certificate is included as part of the SSL connection handshake and the Authorization HTTP header is ignored. Set the scope to rsts:sts:primaryproviderid:certificate or any other identity provider that supports client certificate authentication.

   POST https://<ApplianceIP>/RSTS/oauth2/token

   Host: <ApplianceIP>

   Content-Type: application/json

   Accept: application/json

    

   {

   "grant_type": "client_credentials",

   "scope": "rsts:sts:primaryproviderid:certificate"

   }

2. After successfully authenticating, your response will contain an access_token that must be exchanged for a user token to access the API.

   POST https://<ApplianceIP>/service/core/v2/Token/LoginResponse

   Host: <ApplianceIP>

   Content-Type: application/json

   Accept: application/json

    

   {

   "StsAccessToken": "<access_token from previous response>"

   }

You should now have an authorization token to be used for all future API requests. The token is to be included in the HTTP Authorization header as a Bearer token like this:

For example: