Depending on how the Security Policy Administrator configured the policy, an API key release request will either require approval by one or more Safeguard for Privileged Passwords users, or be auto-approved. Depending on policy configuration, approval can be automatic or require the consent of one or more users which provides closer control over system accounts.
You can revoke a request between the time the requester views it and checks it in.
Any eligible approver can deny an API key release request after it has already been approved or auto-approved. Once disallowed, the requester will no longer have access to the API key, but they are given another opportunity to request that API key again. The requester receives an email notifying them that the request was denied.
Safeguard for Privileged Passwords can be configured to notify you of an API key release request that requires your approval. For more information, see Configuring alerts..
To approve or deny an API key release request
To manage approvals, on the left of the page, click 
Approvals. On the Approvals page, you can:
-
View details by selecting a request, then looking at the details display on the right of the page, including the workflow.
-
Approve one or more request: Select the requests and click 
(Approve all selected requests). Optionally, enter a comment.
-
Deny one or more request: Select the requests and click 
(Deny all selected requests). Optionally, enter a comment.
-
Change the columns that appear: Click 
(Columns) and select the columns you want to see. You can select columns including the following information:
-
Action: Displays (Approve only this request) and (Deny only this request).
-
Requester / Status: Displays the user name and the status of the approval (for example, Pending 1 approval).
-
Asset / Access Type: Displays the name of the asset and the type of access (for example, Password, SSH Key, RDP, SSH, API Key, or Telnet).
-
Account: Displays the managed account name.
-
Ticket Number: Displays the ticket number, if required.
-
Requested For: Displays the date and time as well as the window of availability (for example, March 20, 2021 9:56 AM 2 hours).
-
Search: To see a list of searchable elements, click 
(Search). For more information, see Search box.
The Security Policy Administrator can configure an access request policy to require a review of completed API key release requests for accounts in the scope of the policy.
NOTE: You can configure Safeguard for Privileged Passwords to notify you of an API key release request that requires your review. For more information, see Configuring alerts.
To review a completed API key release request
To manage reviews, on the left of the page, select 
(Reviews). On the Reviews page, you can:
-
View the details of a workflow by selecting it.
-
Mark one or more request as reviewed by selecting the requests, then performing one of the following actions:
-
If no comment is required, click (Mark all the selected requests as reviewed).
-
If a comment is required, this icon will display as (One or more of the selected requests requires review comments). Add the comment, then click Mark as Reviewed.
-
Change the columns that display: Click (Select columns to display) and select the columns you want to see.
-
Action: Displays 
(This request requires review comments) or (Mark only this request as reviewed).
-
Requester: Displays the user name of the requester.
-
Access Type: Displays the type of access (for example, Password, SSH Key, RDP, RDP Application, SSH, API Key, or Telnet).
-
Account: Displays the managed account name.
-
Ticket Number: Displays the ticket number, if required.
-
Request For/Duration: Displays the date and time as well as the window of availability (for example, March 20, 2021 9:56 AM 2 hours).
-
Search: To see a list of searchable elements, click click (Search). For more information, see Search box.
Authorized users can authorize connections, view active connections, limit access to specific resources, be alerted if connections exceed pre-set time limits, and even close connections.
Typically a session request follows the workflow below:
- Request: Users that are designated as an authorized user of an entitlement can request a session for any asset in the scope of that entitlement's policies.
- Approve: Depending on how the Security Policy Administrator configured the policy, a session request will either require approval by one or more Safeguard for Privileged Passwords users, or be auto-approved.
- Review: The Security Policy Administrator can optionally configure an access request policy to require a review of completed requests for assets in the scope of the policy. In addition, if session recording is enabled in the policy, reviewers can audit the workflow transactions and launch the Desktop Player to replay the session as part of the review process.
One Identity Safeguard for Privileged Passwords proxies all sessions to target resources. Users do not have direct access to resources, therefore, the enterprise is protected against viruses, malware or other dangerous items on the user's system. Safeguard can proxy and record Unix/Linux, Windows, network devices, firewalls, routers and more.
NOTE: PuTTY is used to launch the SSH client for SSH session requests and MSTSC is used for RDP session requests. For information on how to setup using PuTTY or MSTSC, see SCALUS.
Important notes
