<?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: Authorization Requests go via second round of the username authentication in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/authorization-requests-go-via-second-round-of-the-username/m-p/4271768#M564764</link>
    <description>&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I got the point of the identity store looks up sequence, but l was surprised to realise that authorization involves that.&lt;/P&gt;&lt;P&gt;Apparently, it's expected behaviour.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Myky&lt;/P&gt;</description>
    <pubDate>Wed, 13 Jan 2021 16:35:26 GMT</pubDate>
    <dc:creator>mykys</dc:creator>
    <dc:date>2021-01-13T16:35:26Z</dc:date>
    <item>
      <title>Authorization Requests go via second round of the username authentication</title>
      <link>https://community.cisco.com/t5/network-access-control/authorization-requests-go-via-second-round-of-the-username/m-p/4271612#M564756</link>
      <description>&lt;P&gt;Hi folks,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I must have missed something basics, but is it expected for ISE to validate username against its identity store for authorization requests?&amp;nbsp;&lt;/P&gt;&lt;P&gt;I always was thinking that once the user is authenticated, its group membership is retrieved during that stage and can be directly used with authorization request (no need to check the same info again).&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Did l miss anything? Log entry below:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="log.PNG" style="width: 587px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/101592i1B270C6DCC324BEE/image-size/large?v=v2&amp;amp;px=999" role="button" title="log.PNG" alt="log.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Myky&lt;/P&gt;</description>
      <pubDate>Wed, 13 Jan 2021 13:33:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/authorization-requests-go-via-second-round-of-the-username/m-p/4271612#M564756</guid>
      <dc:creator>mykys</dc:creator>
      <dc:date>2021-01-13T13:33:08Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization Requests go via second round of the username authentication</title>
      <link>https://community.cisco.com/t5/network-access-control/authorization-requests-go-via-second-round-of-the-username/m-p/4271730#M564763</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/904904"&gt;@mykys&lt;/a&gt;&lt;/P&gt;&lt;P&gt;Your authentication policy seems to reference an identity source sequence where the order states that the first store to check is the internal store. You can see the order in the menu: Administration &amp;gt; Identity Management &amp;gt; Identity Source Sequence. There you will find a sequence with the same name as in your authentication policy. You can change the order in the sequences there or even remove a identity store from the sequence if not needed (although I recommend not to change the default sequences from ISE and instead creating a new one). But be careful with editing this, you have to consider all identities which will be processed by all the authentication rules where this sequence is used.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 13 Jan 2021 15:52:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/authorization-requests-go-via-second-round-of-the-username/m-p/4271730#M564763</guid>
      <dc:creator>martin.fischer</dc:creator>
      <dc:date>2021-01-13T15:52:55Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization Requests go via second round of the username authentication</title>
      <link>https://community.cisco.com/t5/network-access-control/authorization-requests-go-via-second-round-of-the-username/m-p/4271768#M564764</link>
      <description>&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I got the point of the identity store looks up sequence, but l was surprised to realise that authorization involves that.&lt;/P&gt;&lt;P&gt;Apparently, it's expected behaviour.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Myky&lt;/P&gt;</description>
      <pubDate>Wed, 13 Jan 2021 16:35:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/authorization-requests-go-via-second-round-of-the-username/m-p/4271768#M564764</guid>
      <dc:creator>mykys</dc:creator>
      <dc:date>2021-01-13T16:35:26Z</dc:date>
    </item>
  </channel>
</rss>

