SCIM server on prem is not working with Ping OAUTH. throwing client authentication error even though token is generated in postman successfully. documentation talks only about OKTA.

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

SCIM server on prem is not working with Ping OAUTH. throwing client authentication error even though token is generated in postman successfully. documentation talks only about OKTA.

L1 Bithead
4 REPLIES 4

L4 Transporter

When you add and configure the OAuth2 Client application, make sure to use the Login Name identity-privilege-integration-user$

 

Follow this link - https://docs.cyberark.com/identity/latest/en/content/developer/scim-management/scim-server-configuration.htm

L4 Transporter

When you add and configure the OAuth2 Client application, make sure to use the Login Name identity-privilege-integration-user$

 

Follow this link - https://docs.cyberark.com/identity/latest/en/content/developer/scim-management/scim-server-configuration.htm

L1 Bithead

we are on self hosted environment. not using identity. trying to implement oauth using ping. sample values given for oktaconfig.json are as below

 

{ "OktaDomain": "https://okta.xyz.com", "AuthorizationServerId": "default", "Audience": "api://default" }

 

what would be the values for ping

L7 Applicator

Hi @Srinivas B​ 

 

In Postman you can manually generate a token and then use it as a Bearer Token in the authorization header for subsequent requests.This proves that your SCIM server endpoint and the token itself are valid.

 

Whereas PingFederate acts as the OAuth client itself. It must be configured to obtain its own token and then use it for the SCIM requests. 

 

The client authentication error suggests that PingFederate is failing the initial step of authenticating to the SCIM server to get a valid token. This is where the configuration mismatch is most likely occurring.

 

It could be due to incorrect or mismatch in Client ID or Secret configured in PingFederate and SCIM.

 

Also please check that the Client Authentication method in PingFederate is compatible with SCIM server. 

 

Check the PingFederate and SCIM logs for authentication failure or invalid client. That will provide clear information.

 

Hope it helps !

 

 

  • 95 Views
  • 4 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!