<?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: EAP-Chaining UserID based ODBC Query in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/eap-chaining-userid-based-odbc-query/m-p/3520673#M509781</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I believe your case already escalated to our ESC team and being worked on by Dev so it's best for you to continue that route. We could give some random ideas but might do more harms than helpful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am not familiar with MS SQL stored procedures but I am guessing they can do something like this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the subject is a machine, then return empty attribute/group list.&lt;/P&gt;&lt;P&gt;Else &amp;lt;do the regular attribute/group lookup&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PS: I am not Hosuk. &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 22 May 2018 03:44:24 GMT</pubDate>
    <dc:creator>hslai</dc:creator>
    <dc:date>2018-05-22T03:44:24Z</dc:date>
    <item>
      <title>EAP-Chaining UserID based ODBC Query</title>
      <link>https://community.cisco.com/t5/network-access-control/eap-chaining-userid-based-odbc-query/m-p/3520670#M509776</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;My customer has ISE 2.3 Patch 2 integrated with Microsoft SQL 2016 Database. &lt;/P&gt;&lt;P&gt;The design was to have dot1x endpoints to get authenticated against AD and get authorised against SQL DB values for SGT and VLAN. &lt;/P&gt;&lt;P&gt;This is to meet scalability needs, as recommended by ISE TME. &lt;/P&gt;&lt;P&gt;Customer uses Cisco AnyConnect NAM supplicant with EAP-Chaining for both User AND Machine Authentication enabled. &lt;/P&gt;&lt;P&gt;The Table in Microsoft SQL DB consists of User_ID, Project_ID, VLAN and SGT values, and the plan is to authorise endpoints based on User_ID. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The integration with ODBC when clicked on "Test connection" shows working fine. We could also manually fetch attributes from ISE page.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However when connected an endpoint, the endpoint is shown authenticated in ISE log but the SGT and VLAN attributes are not getting assigned. This happens when we have User_ID only in SQL table, with EAP-FAST (AnyConnect NAM with User AND Machine Authentication as Supplicant settings).&lt;/P&gt;&lt;P&gt;I could see the unique error in the ISE log as "Dynamic Attribute value not available". &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It only works,&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;When included the Machine Hostname in the SQL table (host/PUNITP152923L), SQL attributes are fetched and working fine. The endpoint gets respective VLAN and SGT.&lt;/LI&gt;&lt;LI&gt;When tried ONLY with User Authentication (Windows Native Supplicant), the SQL attributes are fetched and working fine. The endpoint gets respective VLAN and SGT.&lt;/LI&gt;&lt;LI&gt;When tried with User or Computer Authentication (MAR – Windows Native Supplicant), the SQL attributes are fetched and working fine. The endpoint gets respective VLAN and SGT.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please help with this, if there is a way to make ISE to send User_ID when querying SQL DB for attributes, instead of Machine Hostname. &lt;/P&gt;&lt;P&gt;Is there any AnyConnect NAM settings to do this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks and Regards&lt;/P&gt;&lt;P&gt;V Vinodh.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 May 2018 17:41:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/eap-chaining-userid-based-odbc-query/m-p/3520670#M509776</guid>
      <dc:creator>junk1</dc:creator>
      <dc:date>2018-05-21T17:41:06Z</dc:date>
    </item>
    <item>
      <title>Re: EAP-Chaining UserID based ODBC Query</title>
      <link>https://community.cisco.com/t5/network-access-control/eap-chaining-userid-based-odbc-query/m-p/3520671#M509777</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;EAP Chaining is a means to authenticate and authorize both the user and the machine, regardless using ODBC or not. If the use case is for user only, then please configure NAM for user auth only.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 May 2018 18:32:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/eap-chaining-userid-based-odbc-query/m-p/3520671#M509777</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2018-05-21T18:32:02Z</dc:date>
    </item>
    <item>
      <title>Re: EAP-Chaining UserID based ODBC Query</title>
      <link>https://community.cisco.com/t5/network-access-control/eap-chaining-userid-based-odbc-query/m-p/3520672#M509779</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Hosuk&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The requirement is to have both User AND Machine Authentication only, as per supplicant settings.&lt;/P&gt;&lt;P&gt;But when it comes to ODBC, the queries should be done based on either User_ID alone or based on the combination of User_ID and Machine name. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here it is happening only based on Machine name.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any way to achieve this with ODBC settings?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;V Vinodh.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 May 2018 03:17:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/eap-chaining-userid-based-odbc-query/m-p/3520672#M509779</guid>
      <dc:creator>junk1</dc:creator>
      <dc:date>2018-05-22T03:17:04Z</dc:date>
    </item>
    <item>
      <title>Re: EAP-Chaining UserID based ODBC Query</title>
      <link>https://community.cisco.com/t5/network-access-control/eap-chaining-userid-based-odbc-query/m-p/3520673#M509781</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I believe your case already escalated to our ESC team and being worked on by Dev so it's best for you to continue that route. We could give some random ideas but might do more harms than helpful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am not familiar with MS SQL stored procedures but I am guessing they can do something like this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the subject is a machine, then return empty attribute/group list.&lt;/P&gt;&lt;P&gt;Else &amp;lt;do the regular attribute/group lookup&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PS: I am not Hosuk. &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 May 2018 03:44:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/eap-chaining-userid-based-odbc-query/m-p/3520673#M509781</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2018-05-22T03:44:24Z</dc:date>
    </item>
    <item>
      <title>Re: EAP-Chaining UserID based ODBC Query</title>
      <link>https://community.cisco.com/t5/network-access-control/eap-chaining-userid-based-odbc-query/m-p/3520674#M509783</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Hsing-Tsu Lai... and apologise for the typo.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;V Vinodh.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 May 2018 04:25:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/eap-chaining-userid-based-odbc-query/m-p/3520674#M509783</guid>
      <dc:creator>junk1</dc:creator>
      <dc:date>2018-05-22T04:25:56Z</dc:date>
    </item>
  </channel>
</rss>

