PrivCloud - User-related APIs return different IDs for same Username depending on which method is queried

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

PrivCloud - User-related APIs return different IDs for same Username depending on which method is queried

L4 Transporter

I am currently writing a utility that retrieves data from my Privilege Cloud ISPSS tenant (such as user info, safe list, safe member info per safe) and sends it to another tool. During my tests, I saw that the information when it comes to user IDs is somewhat inconsistent between API methods.

 

For example: When querying the "Get Users" API method, it returns the id 8 for the user "CyberarkRotationService", but when querying the "Get Safe Members" API method for an internal safe (such as SharedAuth_Internal), the safe member with the name "CyberarkRotationService" has the id "51077119-844d-4c20-b214-5be5d035e499".

 

Anyone ran into an issue like this?

 

 

"Get Users" API Output - Snippet

{     "id": 8,     "username": "CyberarkRotationService",     "source": "CyberArk",     "userType": "Built-InAdmins",     "componentUser": false,     "groupsMembership": [],     "vaultAuthorization": [],     "location": "\\",     "personalDetails": {         "firstName": "",         "middleName": "",         "lastName": "",         "organization": "",         "department": ""     },     "enableUser": false,     "suspended": false,     "UUID": null }

"Get Safe Members" API Output - Snippet

{ "isExpiredMembershipEnable": false, "isPredefinedUser": true, "isReadOnly": true, "memberId": "51077119-844d-4c20-b214-5be5d035e499", "memberName": "CyberarkRotationService", "memberType": "User", "membershipExpirationDate": null, "permissions": { "accessWithoutConfirmation": false, "addAccounts": true, "backupSafe": false, "createFolders": true, "deleteAccounts": true, "deleteFolders": true, "initiateCPMAccountManagementOperations": true, "listAccounts": true, "manageSafe": false, "manageSafeMembers": false, "moveAccountsAndFolders": true, "renameAccounts": true, "requestsAuthorizationLevel1": false, "requestsAuthorizationLevel2": false, "retrieveAccounts": true, "specifyNextAccountContent": true, "unlockAccounts": true, "updateAccountContent": true, "updateAccountProperties": true, "useAccounts": true, "viewAuditLog": true, "viewSafeMembers": true }, "safeName": "SharedAuth_Internal", "safeNumber": 6, "safeUrlId": "SharedAuth_Internal" }

 

3 REPLIES 3

L7 Applicator

Hi @Bernhard Brückler​ 

 

In my understanding, directly correlating d from /api/Users with memberId from the safes API isn't possible currently there is no direct mapping exposed via APIs between them.

 

Can you use username as a primary field for mapping users across API responses?

 

 

Using the username as the identifier is my current workaround, but i don't like it, since i suspect it could lead to collisions if a user is deleted and then recreated with the same username (but obviously different ID).

 

For PAM Self-Hosted APIs I never had this issue, but the architecture is slightly different there.

L4 Transporter

Hadn't noticed that, how very confusing! I guess the difference lies under-the-hood.

 

PrivilegeCloud is still a Vault behind the scenes. So within a Vault (such as PrivilegeCloud) there are internal users which each have an Id, and can be marked as "local" or "external". Normally this would be hidden from view within the PrivilegeCloud ISPSS.

 

CyberArk Identity is a separate IdP, which contains it's own internal database of users (Cloud Users) as well as permitting Federation with external directory services.

 

So depending on the situation a user ID might represent the user's ID within the Cloud Directory, or it might represent the user's ID within an external directory if you are querying Identity APIs. Or if you are querying Privilege Cloud's vault APIs the ID might be the Vault's internal user ID representing that user. When dealing with multiple identity sources, it is always tricky to know how to join them up and what constitutes a truly unique identifier.

 

To further confuse matters, when an external user is coming in via SAML or OIDC the SAML claim might contain a unique identifier as well as a username attribute, which CyberArk Identity will faithfully record.

  • 139 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!