<?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: User ID for ncomputing environment in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/user-id-for-ncomputing-environment/m-p/252930#M71868</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Captive portal would be an option. Just make sure to adjust the time so they dont have to enter their info a bunch of times throughout the day.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;</description>
    <pubDate>Fri, 08 Mar 2019 19:14:10 GMT</pubDate>
    <dc:creator>OtakarKlier</dc:creator>
    <dc:date>2019-03-08T19:14:10Z</dc:date>
    <item>
      <title>User ID for ncomputing environment</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/user-id-for-ncomputing-environment/m-p/252859#M71848</link>
      <description>&lt;P&gt;HI all,&lt;/P&gt;&lt;P&gt;My customer has ncomputing (thin client) environment and all servers are Ubuntu. They wanted to implement User-ID feature in this environment. As we do not have any User ID agent for Linux, how can we get user info? Can we use Captive portal, will that work per session?&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Abhijeet&lt;/P&gt;</description>
      <pubDate>Fri, 08 Mar 2019 11:21:49 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/user-id-for-ncomputing-environment/m-p/252859#M71848</guid>
      <dc:creator>Retired Member</dc:creator>
      <dc:date>2019-03-08T11:21:49Z</dc:date>
    </item>
    <item>
      <title>Re: User ID for ncomputing environment</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/user-id-for-ncomputing-environment/m-p/252930#M71868</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Captive portal would be an option. Just make sure to adjust the time so they dont have to enter their info a bunch of times throughout the day.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Fri, 08 Mar 2019 19:14:10 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/user-id-for-ncomputing-environment/m-p/252930#M71868</guid>
      <dc:creator>OtakarKlier</dc:creator>
      <dc:date>2019-03-08T19:14:10Z</dc:date>
    </item>
    <item>
      <title>Re: User ID for ncomputing environment</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/user-id-for-ncomputing-environment/m-p/252957#M71879</link>
      <description>&lt;P&gt;@Retired Member,&lt;/P&gt;&lt;P&gt;Captive Portal or enforced GlobalProtect would both be a great way of doing something like this. I would personally lean more on the GlobalProtect method, however depending on the skill of your users that might not be something I would want to deal with since the linux GP agent isn't all that refined at the moment.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 08 Mar 2019 21:39:57 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/user-id-for-ncomputing-environment/m-p/252957#M71879</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2019-03-08T21:39:57Z</dc:date>
    </item>
    <item>
      <title>Re: User ID for ncomputing environment</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/user-id-for-ncomputing-environment/m-p/253006#M71889</link>
      <description>&lt;P&gt;Hi, I also though of Captive portal as solution, how ever from Ubuntu server for every session (Ip address being the same) will Captive portal ask for authentication?&lt;/P&gt;</description>
      <pubDate>Sat, 09 Mar 2019 12:52:48 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/user-id-for-ncomputing-environment/m-p/253006#M71889</guid>
      <dc:creator>Retired Member</dc:creator>
      <dc:date>2019-03-09T12:52:48Z</dc:date>
    </item>
  </channel>
</rss>

