<?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: Discovered Identities in FMC in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/discovered-identities-in-fmc/m-p/4963294#M1106059</link>
    <description>&lt;P&gt;Did you ever find a resolution to this?&lt;/P&gt;</description>
    <pubDate>Mon, 20 Nov 2023 22:34:26 GMT</pubDate>
    <dc:creator>NA-School</dc:creator>
    <dc:date>2023-11-20T22:34:26Z</dc:date>
    <item>
      <title>Discovered Identities in FMC</title>
      <link>https://community.cisco.com/t5/network-security/discovered-identities-in-fmc/m-p/4683264#M1093247</link>
      <description>&lt;P&gt;Hello Experts&lt;/P&gt;
&lt;P&gt;I have a customer that has a Firepower Deployment and we have integrated into ISE using PXGrid. We have also created an AD Realm and integrated this via LDAP.&lt;/P&gt;
&lt;P&gt;VPN authentication is making use of a Certificate and when a user logs on or off we can see the User Activity in the FMC under the User Activity but this is mapped to Discovered Identity instead of the AD Realm. We have tried multiple options in the certificate to try and match it against the AD Realm but this doesn't work. If we change the VPN Authentication type to AAA-only or AAA &amp;amp; Certificate then the user is correctly mapped to the AD Realm. The client does not want to make this change on the VPN as he does not want the users to have to enter credentials when accessing the VPN.&lt;/P&gt;
&lt;P&gt;This is impacting the Passive Identity Policy assigned to the Access-Control Policy. We are able to select the relevant AD Group in the rules that are required to have this set but the users never match the rule because of the Discovered Identity match&lt;/P&gt;
&lt;P&gt;Anyone have any ideas how to resolve this?&lt;/P&gt;</description>
      <pubDate>Thu, 08 Sep 2022 08:12:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/discovered-identities-in-fmc/m-p/4683264#M1093247</guid>
      <dc:creator>Steven van Jaarsveld</dc:creator>
      <dc:date>2022-09-08T08:12:59Z</dc:date>
    </item>
    <item>
      <title>Re: Discovered Identities in FMC</title>
      <link>https://community.cisco.com/t5/network-security/discovered-identities-in-fmc/m-p/4683274#M1093248</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/251204"&gt;@Steven van Jaarsveld&lt;/a&gt; I haven't had this exact requirement before....how about still using certificate authentication but send authorisation only to ISE? This would send the username extracted from the certificate, ISE would perform an AD lookup of the username and authorise the user. This would create a session in ISE, which is forwarded to the FMC/FTD.&lt;/P&gt;</description>
      <pubDate>Thu, 08 Sep 2022 08:31:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/discovered-identities-in-fmc/m-p/4683274#M1093248</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2022-09-08T08:31:35Z</dc:date>
    </item>
    <item>
      <title>Re: Discovered Identities in FMC</title>
      <link>https://community.cisco.com/t5/network-security/discovered-identities-in-fmc/m-p/4683336#M1093249</link>
      <description>&lt;P&gt;The &lt;A href="https://ciscocentral.blogspot.com/p/350-901-developing-applications-using.html" target="_self"&gt;Cisco Secure Firewall Management Center (FMC)&lt;/A&gt; is your administrative nerve center for managing critical Cisco network security solutions.&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/products/collateral/security/firesight-management-center/datasheet-c78-736775.html" target="_blank" rel="noopener"&gt;https://www.cisco.com/c/en/us/products/collateral/security/firesight-management-center/datasheet-c78-736775.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 29 Sep 2022 08:29:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/discovered-identities-in-fmc/m-p/4683336#M1093249</guid>
      <dc:creator>alirafaleiro</dc:creator>
      <dc:date>2022-09-29T08:29:29Z</dc:date>
    </item>
    <item>
      <title>Re: Discovered Identities in FMC</title>
      <link>https://community.cisco.com/t5/network-security/discovered-identities-in-fmc/m-p/4963294#M1106059</link>
      <description>&lt;P&gt;Did you ever find a resolution to this?&lt;/P&gt;</description>
      <pubDate>Mon, 20 Nov 2023 22:34:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/discovered-identities-in-fmc/m-p/4963294#M1106059</guid>
      <dc:creator>NA-School</dc:creator>
      <dc:date>2023-11-20T22:34:26Z</dc:date>
    </item>
    <item>
      <title>Re: Discovered Identities in FMC</title>
      <link>https://community.cisco.com/t5/network-security/discovered-identities-in-fmc/m-p/5305160#M1121588</link>
      <description>&lt;P&gt;Any update here.&amp;nbsp;&lt;BR /&gt;I have the same issue with cdFMC. SAML Authentication is working fine but nor realm is discoverd for the user session.&lt;BR /&gt;A SAML Relam is configured in FMC and also an LDAP realm. Authorisation with LDAP has been tested too, but it still won't link the realm to the user.&lt;BR /&gt;&lt;BR /&gt;Has somebody find a solution&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 03 Jul 2025 09:35:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/discovered-identities-in-fmc/m-p/5305160#M1121588</guid>
      <dc:creator>t1m1</dc:creator>
      <dc:date>2025-07-03T09:35:26Z</dc:date>
    </item>
    <item>
      <title>Re: Discovered Identities in FMC</title>
      <link>https://community.cisco.com/t5/network-security/discovered-identities-in-fmc/m-p/5305185#M1121590</link>
      <description>&lt;P&gt;Make new post please&amp;nbsp;&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
      <pubDate>Thu, 03 Jul 2025 10:31:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/discovered-identities-in-fmc/m-p/5305185#M1121590</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2025-07-03T10:31:53Z</dc:date>
    </item>
  </channel>
</rss>

