<?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 Guest / Self-Registration Question in ExtremeCloud IQ- Site Engine Management Center</title>
    <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/guest-self-registration-question/m-p/71770#M8282</link>
    <description>&lt;P&gt;We have a NAC portal with an expiration of 3 days for guests. &amp;nbsp;We have a large permanent group here that also join as guests but are required to use their proper email address - let’s say jim@dudes.com. &amp;nbsp;Any email address with “dudes.com” will get moved to a group called dudes and get their own policy. &amp;nbsp;We’d like to NOT expire dude accounts. &amp;nbsp;We used to collect MAC addresses to MAC auth but as permanent as the group is, the&amp;nbsp;actual clientele is transient enough that that was a pain. &amp;nbsp;It’s easy to search for dude email addresses and move them but difficult to manually change the registration expiration date. &amp;nbsp;Part of the charge from up above&amp;nbsp;is to keep the dude$&amp;nbsp;happy&amp;nbsp;(i..e keep it simple for them). &amp;nbsp;&lt;/P&gt; &lt;P&gt;&amp;nbsp;&lt;/P&gt; &lt;P&gt;Any suggestions on how to change the expiration date en masse&amp;nbsp;AFTER they register or perhaps a retool of the whole idea? &amp;nbsp;(30,000 ft overview of course). &amp;nbsp;Thanks in advance.&lt;/P&gt;</description>
    <pubDate>Sat, 29 Feb 2020 03:50:50 GMT</pubDate>
    <dc:creator>Chris_Sherman</dc:creator>
    <dc:date>2020-02-29T03:50:50Z</dc:date>
    <item>
      <title>Guest / Self-Registration Question</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/guest-self-registration-question/m-p/71770#M8282</link>
      <description>&lt;P&gt;We have a NAC portal with an expiration of 3 days for guests. &amp;nbsp;We have a large permanent group here that also join as guests but are required to use their proper email address - let’s say jim@dudes.com. &amp;nbsp;Any email address with “dudes.com” will get moved to a group called dudes and get their own policy. &amp;nbsp;We’d like to NOT expire dude accounts. &amp;nbsp;We used to collect MAC addresses to MAC auth but as permanent as the group is, the&amp;nbsp;actual clientele is transient enough that that was a pain. &amp;nbsp;It’s easy to search for dude email addresses and move them but difficult to manually change the registration expiration date. &amp;nbsp;Part of the charge from up above&amp;nbsp;is to keep the dude$&amp;nbsp;happy&amp;nbsp;(i..e keep it simple for them). &amp;nbsp;&lt;/P&gt; &lt;P&gt;&amp;nbsp;&lt;/P&gt; &lt;P&gt;Any suggestions on how to change the expiration date en masse&amp;nbsp;AFTER they register or perhaps a retool of the whole idea? &amp;nbsp;(30,000 ft overview of course). &amp;nbsp;Thanks in advance.&lt;/P&gt;</description>
      <pubDate>Sat, 29 Feb 2020 03:50:50 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/guest-self-registration-question/m-p/71770#M8282</guid>
      <dc:creator>Chris_Sherman</dc:creator>
      <dc:date>2020-02-29T03:50:50Z</dc:date>
    </item>
  </channel>
</rss>

