DPA API endpoints session-diagnostics, strong-accounts, and access-policies return 403 for OAuth2 service account with DPAAdmin role. Are these portal-only?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

DPA API endpoints session-diagnostics, strong-accounts, and access-policies return 403 for OAuth2 service account with DPAAdmin role. Are these portal-only?

L1 Bithead

Environment: Privilege Cloud (ISPSS), UAP Only tenant

Auth: client_credentials flow via /oauth2/platformtoken

Service account roles: DPAAdmin, Privilege Cloud Administrators, Privilege Cloud Auditors, Connector Management Admin, global auditor

 

Endpoints that WORK with this service account:

- GET /api/dpa/connectors

- GET /api/dpa/settings

 

Endpoints that return 403 Forbidden:

- GET /api/dpa/session-diagnostics

- GET /api/dpa/strong-accounts/virtual-machines

- GET /api/dpa/policies

 

For access-policies specifically, the error is:

{"code":"DPA_CRUD_ACTION_FAILED","message":"Forbidden","description":"The old policies APIs are blocked, as the tenant's policies status is [UAP Only]. Please use the new APIs."}

 

The UAP API docs (api-docs.cyberark.com/uap-schema-api) indicate the new endpoint is https://<subdomain>.uap.cyberark.cloud/api but this returns AWS API Gateway IncompleteSignatureException with the platformtoken Bearer token.

 

Questions:

1. Are session-diagnostics and strong-accounts supported for OAuth2 service accounts?

2. For UAP tenants, what is the correct auth flow for uap.cyberark.cloud?

3. Is there a permission beyond DPAAdmin required?

 

Ref: Enhancement request 000039221 notes the all-or-nothing nature of DPAAdmin access.

3 REPLIES 3

L5 Sessionator

Hey @Stuart Riesen​ 

 

1. Can you provide the documentation link you're referring to for the /api/dpa/* endpoints?

2. To Create an API token - https://api-docs.cyberark.com/create-api-token/docs/create-api-token

3. For UAP, we recommend using a dedicated service user with the CS Admin or SCA Admin role for cloud console policies, or the DPAAdmin role for infrastructure policies:

https://api-docs.cyberark.com/uap-schema-api/docs/get-started

L1 Bithead

Thanks @Patrick Booth​  - here are the specifics:

 

1. Documentation references:

  - VM access policies API: https://docs.cyberark.com/ispss-access/latest/en/content/apis/dpa_policies.htm

  - This page states "To run this API, you must have the DpaAdmin role"

  - It also notes our tenant uses UAP and points to https://api-docs.cyberark.com/uap-schema-api/

 

2. We are using the platformtoken endpoint per the docs you linked. 

  Auth works - the same token successfully calls:

  - GET /api/dpa/connectors [works]

  - GET /api/dpa/settings [works]

 

3. The same token with DPAAdmin role gets 403 on:

  - GET /api/dpa/session-diagnostics [403 Forbidden]

  - GET /api/dpa/strong-accounts/virtual-machines [403 Forbidden]

  - GET /api/dpa/policies [403 Forbidden]

  - GET /api/dpa/access-policies [blocked - returns: "The old policies APIs are blocked, as the tenant's policies status is [UAP Only]. Please use the new APIs."]

 

4. For the UAP endpoint (https://<subdomain>.uap.cyberark.cloud/api/access-policies) using the Bearer token from platformtoken, we get:

  HTTP 403 with x-amzn-ErrorType: IncompleteSignatureException "Authorization header requires 'Credential' parameter. Authorization header requires 'Signature' parameter."

 

This suggests the UAP API Gateway expects AWS SigV4 auth, not a Bearer token. Is there an intermediate token exchange step we are missing?

 

The service account has: DPAAdmin, Privilege Cloud Administrators, 

Privilege Cloud Auditors, Connector Management Admin, global auditor.

Were you able to resolve this issue . I am exactly in same problem.

  • 73 Views
  • 3 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!