<?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 Re: SCIM with Azure not working in Workforce Identity Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/scim-with-azure-not-working/m-p/1367183#M906</link>
    <description>&lt;P&gt;Not sure what you mean in step 1, the token is generated from CyberArk Identity and doesn't exist in Azure itself so there is no way to give it permissions apart from the scope. For step 2 and 3 these have been verified.&lt;/P&gt;</description>
    <pubDate>Mon, 18 Dec 2023 15:04:29 GMT</pubDate>
    <dc:creator>AJensen</dc:creator>
    <dc:date>2023-12-18T15:04:29Z</dc:date>
    <item>
      <title>SCIM with Azure not working</title>
      <link>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/scim-with-azure-not-working/m-p/1367181#M904</link>
      <description>&lt;P&gt;I am having issues with SCIM not working with Azure, this is for cloud. I've followed the documentation below but when testing the connection in Azure it says invalid credentials. The credentials are correct as I am able to make calls to the SCIM endpoints via Postman with the same token. Azure support can't seem to find the issue and CyberArk support says there is no issue. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone run into this issue before or has anyone been able to successfully integrate SCIM with Azure?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The endpoint I am using is https://&amp;lt;tenantURL&amp;gt;.id.cyberark.cloud/scim/&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;https://docs.cyberark.com/Idaptive/Latest/en/Content/CoreServices/UsersRoles/SCIM-AAD.htm?TocPath=Set%20up%20CyberArk%20Identity%7CAdd%20Users%7C_____4&lt;/P&gt;</description>
      <pubDate>Fri, 15 Dec 2023 15:57:02 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/scim-with-azure-not-working/m-p/1367181#M904</guid>
      <dc:creator>AJensen</dc:creator>
      <dc:date>2023-12-15T15:57:02Z</dc:date>
    </item>
    <item>
      <title>Re: SCIM with Azure not working</title>
      <link>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/scim-with-azure-not-working/m-p/1367182#M905</link>
      <description>&lt;P&gt;Hi @Alex Jensen​&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I would check the following in this situation,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Double-check that the token you are using for SCIM integration has the necessary permissions in Azure AD. Ensure it has the required SCIM-related permissions for user&lt;/LI&gt;&lt;LI&gt;Verify that the endpoint configurations in Azure match the SCIM endpoint configurations in CyberArk. Pay attention to the base URL, authentication method, and other relevant settings&lt;/LI&gt;&lt;LI&gt;Confirm the validity period of the token used for SCIM integration. Ensure it has not expired, and check if there are any token-related issues that might cause authentication failures.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope this helps !&lt;/P&gt;</description>
      <pubDate>Fri, 15 Dec 2023 21:35:56 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/scim-with-azure-not-working/m-p/1367182#M905</guid>
      <dc:creator>M.Vora780263</dc:creator>
      <dc:date>2023-12-15T21:35:56Z</dc:date>
    </item>
    <item>
      <title>Re: SCIM with Azure not working</title>
      <link>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/scim-with-azure-not-working/m-p/1367183#M906</link>
      <description>&lt;P&gt;Not sure what you mean in step 1, the token is generated from CyberArk Identity and doesn't exist in Azure itself so there is no way to give it permissions apart from the scope. For step 2 and 3 these have been verified.&lt;/P&gt;</description>
      <pubDate>Mon, 18 Dec 2023 15:04:29 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/scim-with-azure-not-working/m-p/1367183#M906</guid>
      <dc:creator>AJensen</dc:creator>
      <dc:date>2023-12-18T15:04:29Z</dc:date>
    </item>
  </channel>
</rss>

