<?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 Cloud Identity Engine Group Mapping in Cloud Identity Engine Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cloud-identity-engine/cloud-identity-engine-group-mapping/m-p/540828#M42</link>
    <description>&lt;P&gt;It seems like guest users arent matching any groups with Cloud Identity Engine. We have SAML (Azure) setup for our GlobalProtect authentication (not throught Cloud Identity Engine). We have CIE configured on the firewall under user identification. The Cloud Identity Engine is configured to sync the Azure directory but if I look on the firewall using&amp;nbsp;show user user-ids match-user it shows no groups. We have on-prem users that sync up to Azure and those pull groups fine however the guest accounts do not, so accounta we invite into Azure and arent synced on prem dont match any groups.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If I go to CIE itself I can see the user there and the groups they are a part of but the firewall doesnt pull any of those groups, the certain groups are used for different agent configs for GlobalProtect. Is there a reason if wouldn't be pulling the groups that it should need? Do I need to use a SAML auth profile through CIE itself?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Running command "show user cloud-identity-engine statistics all" returns&amp;nbsp;Failed with error code: -20001&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://docs.paloaltonetworks.com/cloud-identity/cloud-identity-engine-getting-started/authenticate-users-with-the-cloud-identity-engine/configure-the-cloud-identity-engine-as-a-mapping-source-on-the-firewall" target="_blank" rel="noopener"&gt;Configure the Cloud Identity Engine as a Mapping Source on the Firewall (paloaltonetworks.com)&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 02 May 2023 22:41:09 GMT</pubDate>
    <dc:creator>Claw4609</dc:creator>
    <dc:date>2023-05-02T22:41:09Z</dc:date>
    <item>
      <title>Cloud Identity Engine Group Mapping</title>
      <link>https://live.paloaltonetworks.com/t5/cloud-identity-engine/cloud-identity-engine-group-mapping/m-p/540828#M42</link>
      <description>&lt;P&gt;It seems like guest users arent matching any groups with Cloud Identity Engine. We have SAML (Azure) setup for our GlobalProtect authentication (not throught Cloud Identity Engine). We have CIE configured on the firewall under user identification. The Cloud Identity Engine is configured to sync the Azure directory but if I look on the firewall using&amp;nbsp;show user user-ids match-user it shows no groups. We have on-prem users that sync up to Azure and those pull groups fine however the guest accounts do not, so accounta we invite into Azure and arent synced on prem dont match any groups.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If I go to CIE itself I can see the user there and the groups they are a part of but the firewall doesnt pull any of those groups, the certain groups are used for different agent configs for GlobalProtect. Is there a reason if wouldn't be pulling the groups that it should need? Do I need to use a SAML auth profile through CIE itself?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Running command "show user cloud-identity-engine statistics all" returns&amp;nbsp;Failed with error code: -20001&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://docs.paloaltonetworks.com/cloud-identity/cloud-identity-engine-getting-started/authenticate-users-with-the-cloud-identity-engine/configure-the-cloud-identity-engine-as-a-mapping-source-on-the-firewall" target="_blank" rel="noopener"&gt;Configure the Cloud Identity Engine as a Mapping Source on the Firewall (paloaltonetworks.com)&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 02 May 2023 22:41:09 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cloud-identity-engine/cloud-identity-engine-group-mapping/m-p/540828#M42</guid>
      <dc:creator>Claw4609</dc:creator>
      <dc:date>2023-05-02T22:41:09Z</dc:date>
    </item>
    <item>
      <title>Re: Cloud Identity Engine Group Mapping</title>
      <link>https://live.paloaltonetworks.com/t5/cloud-identity-engine/cloud-identity-engine-group-mapping/m-p/543157#M44</link>
      <description>&lt;P&gt;Try using SCIM in Azure AD and then refence the CIE in the firewall auth profile:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://docs.paloaltonetworks.com/cloud-identity/cloud-identity-engine-getting-started/authenticate-users-with-the-cloud-identity-engine/configure-the-cloud-identity-engine-in-an-authentication-profile" target="_blank"&gt;https://docs.paloaltonetworks.com/cloud-identity/cloud-identity-engine-getting-started/authenticate-users-with-the-cloud-identity-engine/configure-the-cloud-identity-engine-in-an-authentication-profile&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://docs.paloaltonetworks.com/cloud-identity/cloud-identity-engine-getting-started/choose-directory-type/configure-a-cloud-based-directory/configure-scim-connector-for-the-cloud-identity-engine" target="_blank"&gt;https://docs.paloaltonetworks.com/cloud-identity/cloud-identity-engine-getting-started/choose-directory-type/configure-a-cloud-based-directory/configure-scim-connector-for-the-cloud-identity-engine&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 24 May 2023 08:52:52 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cloud-identity-engine/cloud-identity-engine-group-mapping/m-p/543157#M44</guid>
      <dc:creator>nikoolayy1</dc:creator>
      <dc:date>2023-05-24T08:52:52Z</dc:date>
    </item>
    <item>
      <title>Re: Cloud Identity Engine Group Mapping</title>
      <link>https://live.paloaltonetworks.com/t5/cloud-identity-engine/cloud-identity-engine-group-mapping/m-p/552878#M48</link>
      <description>&lt;P&gt;i'm having exactly the same issue. did you end up solving this?&lt;/P&gt;</description>
      <pubDate>Tue, 08 Aug 2023 06:55:40 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cloud-identity-engine/cloud-identity-engine-group-mapping/m-p/552878#M48</guid>
      <dc:creator>sdoorey01</dc:creator>
      <dc:date>2023-08-08T06:55:40Z</dc:date>
    </item>
    <item>
      <title>Re: Cloud Identity Engine Group Mapping</title>
      <link>https://live.paloaltonetworks.com/t5/cloud-identity-engine/cloud-identity-engine-group-mapping/m-p/552991#M49</link>
      <description>&lt;P&gt;Opened a TAC case on it and ours ended up being an error/bug with the user-id service on the firewall side. We restarted the service and it fixed the issue.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Commands ran:&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;gt;debug software restart process user-id-agent&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt;debug user-id refresh group-mapping all&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;The error we were getting was shown in the&amp;nbsp;dscd.log file. Cli command for that:&amp;nbsp;less mp-log dscd.log&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 08 Aug 2023 21:00:09 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cloud-identity-engine/cloud-identity-engine-group-mapping/m-p/552991#M49</guid>
      <dc:creator>Claw4609</dc:creator>
      <dc:date>2023-08-08T21:00:09Z</dc:date>
    </item>
    <item>
      <title>Re: Cloud Identity Engine Group Mapping</title>
      <link>https://live.paloaltonetworks.com/t5/cloud-identity-engine/cloud-identity-engine-group-mapping/m-p/553601#M50</link>
      <description>&lt;P&gt;dscd is the process for the cloud identity engine connection from the firewall, so this explains the workaround.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Edit: Also you could automate the process restart each night till you upgrade to a stable version following article:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/t5/general-articles/automating-the-palo-alto-ngfw-s-process-deamon-restarts/ta-p/529328#M605" target="_blank"&gt;https://live.paloaltonetworks.com/t5/general-articles/automating-the-palo-alto-ngfw-s-process-deamon-restarts/ta-p/529328#M605&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 21 Aug 2023 06:26:22 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cloud-identity-engine/cloud-identity-engine-group-mapping/m-p/553601#M50</guid>
      <dc:creator>nikoolayy1</dc:creator>
      <dc:date>2023-08-21T06:26:22Z</dc:date>
    </item>
  </channel>
</rss>

