- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
03-01-2024 12:20 PM
Hello. We're currently trying to setup our on-prem SCIM server to use Oauth but the instructions from CyberArk are very vague. Has anyone configured their on-prem SCIM to use Oauth? And if so, can you help us out?
03-05-2024 12:56 AM
An update here, @Scott Swanson I think it should be possible using external IdP if you are not using CyberArk Identity.
Just at a high level,
Hope it helps !
03-04-2024 08:18 PM
Hi Scott (@Scott Swanson),
Understand you are in need of more detailed instructions for configuring your on-prem SCIM to use Oauth. Not sure if you've already seen this documentation, but if not, this may provide the specific step-by-step instructions you're needing.
Hope this helps!
-Sal (Community Manager)
03-05-2024 12:38 AM
Hi @Sal Linscheid
If I understand correctly then the OAUTH is supported when using CyberArk Identity and not on self-hosted environment. Is this understanding correct?
Thanks !
03-05-2024 12:56 AM
An update here, @Scott Swanson I think it should be possible using external IdP if you are not using CyberArk Identity.
Just at a high level,
Hope it helps !
03-05-2024 06:59 AM
Hi @Malhar Vora,
The following document discusses "CyberArk Identity supports managing privileged accounts and objects in CyberArk Privileged Access Manager - Self-Hosted" and has a section that details about the need to include an OAuth2 Client app in order to access the SCIM server.
Not sure if this adequately answers your question but take a look and see what you think.
Manage privileged objects in CyberArk PAM - Self-Hosted
Regards,
-Sal
03-05-2024 07:11 AM
Hi @Sal Linscheid ,
Thanks for the doc. It looks like the doc is for on-prem PAM environment but using the SaaS version of SCIM. I grabbed the instructions from the Marketplace at this location:
https://caintegrations.s3.amazonaws.com/documentation/CyberArk%20SCIM%20Server%20Implementation%20Guide%20%2823-12-07%29Final.pdf?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAYWENXPZ3AXQOCYSS/20240305/eu-central-1/s3/aws4_request&X-Amz-Date=20240305T150911Z&X-Amz-Expires=360000&X-Amz-SignedHeaders=host&X-Amz-Signature=d03286bd0348e92b0b6c3e5ae864fdea6fcde36f5b55fb9bac7470ab370b940d.
To give full back story, we're integrating our on-prem PAM with Savyint. We're required to use Oauth for the connection between Savyint and our CyberArk environment. The instructions in the above URL seem very vague. Even our Azure engineer was puzzled.
03-05-2024 07:36 AM
@Scott Swanson ,
Thank you for sharing the additional background details. I'll run this past some of our experts to see if they can point us to some other documentation that provides clarity.
-Sal
03-05-2024 08:49 AM
Hi @Scott Swanson,
I received some input from Elijah Hopkins (Security Architect) in which he asked me to clarify whether you're using CyberArk Identity in this integration? He mentioned that if you are using Identity, the document you shared the link for is not the right one as it is for the 'old' SCIM integration.
He did share a plethora of other resources which may help you navigate this effort:
CyberArk Identity setup (SCIM for users and groups)
Understanding all the CyberArk SCIM offerings:
It's a lot to chew on, but hope this information helps as you push forward.
-Sal
03-05-2024 02:36 PM
Thanks @Sal Linscheid for sharing this information
03-05-2024 02:54 PM
Hi @Scott Swanson,
What version of self-hosted PAM are you using? It would be preferable to use the Identity SCIM integration rather than the old SCIM Server integration.
One of our engineers mentioned that SCM server integration only supported Sailpoint. CyberArk does not have a partnership with Savyint at this time.
-Sal
03-05-2024 03:27 PM
We are using on-prem CyberArk PAS and on-prem SCIM. We found a doc we're going to try tomorrow. This should go in conjunction with consumers of our on-prem SCIM to use oauth.
https://docs.cyberark.com/pam-self-hosted/12.6/en/Content/PAS%20INST/OIDC-Authentication.htm?tocpath=Administrator%7CUser%20Management%7CAuthenticate%20to%20Privileged%20Access%20Manager%20-%20Self-Hosted%7CConfigure%20authentication%20methods%7C_____9
03-05-2024 06:56 PM
@Scott Swanson - thanks for the additional details. Hope you have some good success tomorrow - let us know.
-Sal
03-06-2024 08:55 AM
We got a little further. We configured OIDC per the article. We're successfully authenticating to Azure but when routed back to PVWA we get an authentication error:
"ITATS701E External user authentication failure. Reason: ITATS531E External User or Group [UPN formatted name] has not been defined in Users Directory."
We also have another auth method for DUO that returns my samaccountname and works. Is there somewhere we need to change what is being sent from UPN to samaccountname or have PVWA accept the UPN?
03-06-2024 06:43 PM
@Scott Swanson - that's great to hear Scott!
I did get some additional input from one of our Senior Solutions Engineers, which may prove helpful.
Hope this helps you press forward.
-Sal
03-08-2024 07:23 AM
Thanks Sal. This helps. I forwarded your message to our Azure engineer. Here's his response:
"I’m still not seeing what name to send the SamAccontName as. For example if it were SAML you can change the “NameID” from sending UPN to sending SamAccountName. However for OAUTH there is no NameID. So we can add the SamAccountName to the token, we’re doing that now however it will only work if we know what name the app is expecting for this claim so the app can consume it. In the screenshot below it’s the name we really need, we’ve tried a few but we’re sort of guessing."
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!

