<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic 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. in PAM Self-Hosted Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/scim-server-on-prem-is-not-working-with-ping-oauth-throwing/m-p/1409361#M84702</link>
    <description />
    <pubDate>Thu, 31 Jul 2025 13:23:32 GMT</pubDate>
    <dc:creator>S.B841460227367</dc:creator>
    <dc:date>2025-07-31T13:23:32Z</dc:date>
    <item>
      <title>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.</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/scim-server-on-prem-is-not-working-with-ping-oauth-throwing/m-p/1409361#M84702</link>
      <description />
      <pubDate>Thu, 31 Jul 2025 13:23:32 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/scim-server-on-prem-is-not-working-with-ping-oauth-throwing/m-p/1409361#M84702</guid>
      <dc:creator>S.B841460227367</dc:creator>
      <dc:date>2025-07-31T13:23:32Z</dc:date>
    </item>
    <item>
      <title>Re: 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.</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/scim-server-on-prem-is-not-working-with-ping-oauth-throwing/m-p/1409362#M84703</link>
      <description>&lt;P&gt;When you add and configure the OAuth2 Client application, make sure to use the Login Name identity-privilege-integration-user$&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Follow this link - https://docs.cyberark.com/identity/latest/en/content/developer/scim-management/scim-server-configuration.htm&lt;/P&gt;</description>
      <pubDate>Fri, 01 Aug 2025 08:02:32 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/scim-server-on-prem-is-not-working-with-ping-oauth-throwing/m-p/1409362#M84703</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-08-01T08:02:32Z</dc:date>
    </item>
    <item>
      <title>Re: 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.</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/scim-server-on-prem-is-not-working-with-ping-oauth-throwing/m-p/1409363#M84704</link>
      <description>&lt;P&gt;When you add and configure the OAuth2 Client application, make sure to use the Login Name identity-privilege-integration-user$&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Follow this link - https://docs.cyberark.com/identity/latest/en/content/developer/scim-management/scim-server-configuration.htm&lt;/P&gt;</description>
      <pubDate>Fri, 01 Aug 2025 08:02:32 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/scim-server-on-prem-is-not-working-with-ping-oauth-throwing/m-p/1409363#M84704</guid>
      <dc:creator>SKumar_IIA1</dc:creator>
      <dc:date>2025-08-01T08:02:32Z</dc:date>
    </item>
    <item>
      <title>Re: 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.</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/scim-server-on-prem-is-not-working-with-ping-oauth-throwing/m-p/1409364#M84705</link>
      <description>&lt;P&gt;we are on self hosted environment. not using identity. trying to implement oauth using ping. sample values given for oktaconfig.json are as below&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;{ "OktaDomain": "https://okta.xyz.com", "AuthorizationServerId": "default", "Audience": "api://default" }&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;what would be the values for ping &lt;/P&gt;</description>
      <pubDate>Fri, 01 Aug 2025 08:27:01 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/scim-server-on-prem-is-not-working-with-ping-oauth-throwing/m-p/1409364#M84705</guid>
      <dc:creator>S.B841460227367</dc:creator>
      <dc:date>2025-08-01T08:27:01Z</dc:date>
    </item>
    <item>
      <title>Re: 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.</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/scim-server-on-prem-is-not-working-with-ping-oauth-throwing/m-p/1409365#M84706</link>
      <description>&lt;P&gt;Hi @Srinivas B​&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In Postman you can manually generate a token and then use it as a Bearer Token in the&amp;nbsp;authorization header for subsequent requests.This proves that your SCIM server endpoint and the token itself are valid.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Whereas PingFederate acts as the OAuth client itself.&amp;nbsp;It must be configured to obtain its own token and then use it for the SCIM requests.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The client authentication error suggests that PingFederate is failing the initial step of authenticating to the SCIM server to get a valid token.&amp;nbsp;This is where the configuration mismatch is most likely occurring.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It could be due to incorrect or mismatch in Client ID or Secret configured in PingFederate and SCIM.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also please check that the&amp;nbsp;Client Authentication&amp;nbsp;method in PingFederate is compatible with SCIM server.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Check the PingFederate and SCIM logs for authentication failure or invalid client. That will provide clear information.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope it helps !&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 01 Aug 2025 11:49:22 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/scim-server-on-prem-is-not-working-with-ping-oauth-throwing/m-p/1409365#M84706</guid>
      <dc:creator>M.Vora780263</dc:creator>
      <dc:date>2025-08-01T11:49:22Z</dc:date>
    </item>
  </channel>
</rss>

