<?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 Create custom guest user names in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/create-custom-guest-user-names/m-p/3604516#M535717</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a question from a customer regarding creating custom guest usernames. What they want to achieve is basically this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Guest email is some_user@some_domain -------&amp;gt; Guest username becomes random_username@custom_suffix. The idea is to use one custom suffix for all guest users (i.e. guests.local), having the option to select from different suffixes is nice to have as well. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;They have multiple ISE deployments on their network serving different customers and relying a lot on forwarding requests based on suffixes. For guest users though they do not want to use email addresses as usernames due to their privacy policies and want to use a custom suffix to forward guest authentication to the appropriate ISE deployment. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is this something that can be done?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 02 Jun 2017 09:14:14 GMT</pubDate>
    <dc:creator>ppsychog</dc:creator>
    <dc:date>2017-06-02T09:14:14Z</dc:date>
    <item>
      <title>Create custom guest user names</title>
      <link>https://community.cisco.com/t5/network-access-control/create-custom-guest-user-names/m-p/3604516#M535717</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a question from a customer regarding creating custom guest usernames. What they want to achieve is basically this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Guest email is some_user@some_domain -------&amp;gt; Guest username becomes random_username@custom_suffix. The idea is to use one custom suffix for all guest users (i.e. guests.local), having the option to select from different suffixes is nice to have as well. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;They have multiple ISE deployments on their network serving different customers and relying a lot on forwarding requests based on suffixes. For guest users though they do not want to use email addresses as usernames due to their privacy policies and want to use a custom suffix to forward guest authentication to the appropriate ISE deployment. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is this something that can be done?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Jun 2017 09:14:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/create-custom-guest-user-names/m-p/3604516#M535717</guid>
      <dc:creator>ppsychog</dc:creator>
      <dc:date>2017-06-02T09:14:14Z</dc:date>
    </item>
    <item>
      <title>Re: Create custom guest user names</title>
      <link>https://community.cisco.com/t5/network-access-control/create-custom-guest-user-names/m-p/3604517#M535718</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You cannot set the username via the sponsor portal but you can do this via the API with some outside development work&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please get customer names and use case to the ise product management team through your sales channel&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sent from my iPhone&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Jun 2017 12:42:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/create-custom-guest-user-names/m-p/3604517#M535718</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2017-06-02T12:42:07Z</dc:date>
    </item>
  </channel>
</rss>

