<?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 Using ISE BYOD Onboarding with SAML and MFA in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/using-ise-byod-onboarding-with-saml-and-mfa/m-p/3938787#M456551</link>
    <description>&lt;P&gt;hi experts,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Based on the following post: &lt;A href="https://community.cisco.com/t5/security-documents/notes-on-okta-as-saml-idp/ta-p/3644284" target="_blank"&gt;https://community.cisco.com/t5/security-documents/notes-on-okta-as-saml-idp/ta-p/3644284&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I have the following question:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a customer that has successfully deployed SAML using Okta. SAML has been enabled on the BYOD and Mydevices portal and there are no issues when users authenticate.&lt;/P&gt;&lt;P&gt;The problem with this customer is that endpoints that has been enrolled via BYOD onboarding are not showing within the Mydevices portal when SAML is configured.&lt;/P&gt;&lt;P&gt;If AD/LDAP is used, everything works well.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is this the expected when using SAML? I assume the endpoints gets mapped differently when using this service and, hence, MyDevice portal DB does not see the association (?)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I also suggested to use Okta as a external radius server. However, they want to discard the option of "push" notification or any other that involves a phone. They prefer the extra MFA that is included in the Okta portal when the users gets redirected there.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thanks in advance,&lt;/P&gt;</description>
    <pubDate>Thu, 10 Oct 2019 13:59:28 GMT</pubDate>
    <dc:creator>Roberto.Carmona</dc:creator>
    <dc:date>2019-10-10T13:59:28Z</dc:date>
    <item>
      <title>Using ISE BYOD Onboarding with SAML and MFA</title>
      <link>https://community.cisco.com/t5/network-access-control/using-ise-byod-onboarding-with-saml-and-mfa/m-p/3938787#M456551</link>
      <description>&lt;P&gt;hi experts,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Based on the following post: &lt;A href="https://community.cisco.com/t5/security-documents/notes-on-okta-as-saml-idp/ta-p/3644284" target="_blank"&gt;https://community.cisco.com/t5/security-documents/notes-on-okta-as-saml-idp/ta-p/3644284&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I have the following question:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a customer that has successfully deployed SAML using Okta. SAML has been enabled on the BYOD and Mydevices portal and there are no issues when users authenticate.&lt;/P&gt;&lt;P&gt;The problem with this customer is that endpoints that has been enrolled via BYOD onboarding are not showing within the Mydevices portal when SAML is configured.&lt;/P&gt;&lt;P&gt;If AD/LDAP is used, everything works well.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is this the expected when using SAML? I assume the endpoints gets mapped differently when using this service and, hence, MyDevice portal DB does not see the association (?)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I also suggested to use Okta as a external radius server. However, they want to discard the option of "push" notification or any other that involves a phone. They prefer the extra MFA that is included in the Okta portal when the users gets redirected there.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thanks in advance,&lt;/P&gt;</description>
      <pubDate>Thu, 10 Oct 2019 13:59:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/using-ise-byod-onboarding-with-saml-and-mfa/m-p/3938787#M456551</guid>
      <dc:creator>Roberto.Carmona</dc:creator>
      <dc:date>2019-10-10T13:59:28Z</dc:date>
    </item>
    <item>
      <title>Re: Using ISE BYOD Onboarding with SAML and MFA</title>
      <link>https://community.cisco.com/t5/network-access-control/using-ise-byod-onboarding-with-saml-and-mfa/m-p/3939208#M456554</link>
      <description>Your assumption is correct. I would suggest getting a tac case logged against it so it can be investigated. I’ll forward this to our engineers on BYOD as well&lt;BR /&gt;</description>
      <pubDate>Fri, 11 Oct 2019 11:53:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/using-ise-byod-onboarding-with-saml-and-mfa/m-p/3939208#M456554</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2019-10-11T11:53:54Z</dc:date>
    </item>
    <item>
      <title>Re: Using ISE BYOD Onboarding with SAML and MFA</title>
      <link>https://community.cisco.com/t5/network-access-control/using-ise-byod-onboarding-with-saml-and-mfa/m-p/3939386#M456557</link>
      <description>&lt;P&gt;Thanks Jason,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I believe the customer already opened a tac case and the answer was that this is not supported.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I assume, if they go with Okta as radius server instead of SAML, they will be able to see onboarded devices within the Mydevice portal, right?&lt;/P&gt;</description>
      <pubDate>Fri, 11 Oct 2019 16:41:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/using-ise-byod-onboarding-with-saml-and-mfa/m-p/3939386#M456557</guid>
      <dc:creator>Roberto.Carmona</dc:creator>
      <dc:date>2019-10-11T16:41:08Z</dc:date>
    </item>
    <item>
      <title>Re: Using ISE BYOD Onboarding with SAML and MFA</title>
      <link>https://community.cisco.com/t5/network-access-control/using-ise-byod-onboarding-with-saml-and-mfa/m-p/3943094#M456561</link>
      <description>yes likely but they would have to validate as we don't test that</description>
      <pubDate>Fri, 18 Oct 2019 07:38:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/using-ise-byod-onboarding-with-saml-and-mfa/m-p/3943094#M456561</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2019-10-18T07:38:54Z</dc:date>
    </item>
  </channel>
</rss>

