<?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 NAC sponsorship login  via url in Analytics &amp; Visibility</title>
    <link>https://community.extremenetworks.com/t5/analytics-visibility/nac-sponsorship-login-via-url/m-p/51747#M68</link>
    <description>Hi @ all&lt;BR /&gt;
&lt;BR /&gt;
We configured guest portal with sponsorship required. The sponsor receives the request with url https://&lt;NAC_IP&gt;/sponsor. Especially on mobile devices the login process is complicated and has a poor user experience. Is it possible to genereate "autologin" URLs in the sponsorship request that the sponsor clicks on the link and is automatically "logged in". &lt;BR /&gt;
&lt;BR /&gt;
I know this would be no real login but for sponsorship approvements this would mostly fits the requirement. &lt;BR /&gt;
&lt;BR /&gt;
Any ideas or would that be a feature request?&lt;BR /&gt;
&lt;BR /&gt;
Best Regards&lt;BR /&gt;
Michael&lt;/NAC_IP&gt;</description>
    <pubDate>Tue, 06 May 2014 13:08:00 GMT</pubDate>
    <dc:creator>Michael_Kirchne</dc:creator>
    <dc:date>2014-05-06T13:08:00Z</dc:date>
    <item>
      <title>NAC sponsorship login  via url</title>
      <link>https://community.extremenetworks.com/t5/analytics-visibility/nac-sponsorship-login-via-url/m-p/51747#M68</link>
      <description>Hi @ all&lt;BR /&gt;
&lt;BR /&gt;
We configured guest portal with sponsorship required. The sponsor receives the request with url https://&lt;NAC_IP&gt;/sponsor. Especially on mobile devices the login process is complicated and has a poor user experience. Is it possible to genereate "autologin" URLs in the sponsorship request that the sponsor clicks on the link and is automatically "logged in". &lt;BR /&gt;
&lt;BR /&gt;
I know this would be no real login but for sponsorship approvements this would mostly fits the requirement. &lt;BR /&gt;
&lt;BR /&gt;
Any ideas or would that be a feature request?&lt;BR /&gt;
&lt;BR /&gt;
Best Regards&lt;BR /&gt;
Michael&lt;/NAC_IP&gt;</description>
      <pubDate>Tue, 06 May 2014 13:08:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/analytics-visibility/nac-sponsorship-login-via-url/m-p/51747#M68</guid>
      <dc:creator>Michael_Kirchne</dc:creator>
      <dc:date>2014-05-06T13:08:00Z</dc:date>
    </item>
    <item>
      <title>RE: NAC sponsorship login  via url</title>
      <link>https://community.extremenetworks.com/t5/analytics-visibility/nac-sponsorship-login-via-url/m-p/51748#M69</link>
      <description>Hi there any news regarding this? Is this considered in future releases?&lt;BR /&gt;</description>
      <pubDate>Wed, 18 Jun 2014 16:58:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/analytics-visibility/nac-sponsorship-login-via-url/m-p/51748#M69</guid>
      <dc:creator>Michael_Kirchne</dc:creator>
      <dc:date>2014-06-18T16:58:00Z</dc:date>
    </item>
    <item>
      <title>RE: NAC sponsorship login  via url</title>
      <link>https://community.extremenetworks.com/t5/analytics-visibility/nac-sponsorship-login-via-url/m-p/51749#M70</link>
      <description>Hi @ all&lt;BR /&gt;
&lt;BR /&gt;
Is there any progress regarding this feature request? A new customer asked me this today again. It would be nice if the email could contain a link like&lt;BR /&gt;
&lt;BR /&gt;
https://&lt;NAC_IP&gt;/sponsor?token=3f3f783tf8chedgf6832ft3qweif314rf&lt;BR /&gt;
&lt;BR /&gt;
Of course - this is not a secure login but would fit the requirements of many customers.&lt;BR /&gt;
&lt;BR /&gt;
Regards&lt;BR /&gt;
Michael&lt;/NAC_IP&gt;</description>
      <pubDate>Wed, 17 Dec 2014 22:55:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/analytics-visibility/nac-sponsorship-login-via-url/m-p/51749#M70</guid>
      <dc:creator>Michael_Kirchne</dc:creator>
      <dc:date>2014-12-17T22:55:00Z</dc:date>
    </item>
  </channel>
</rss>

