<?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: Enterprise Guide and Windows Authentication in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/Enterprise-Guide-and-Windows-Authentication/m-p/140066#M1604</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Check the IWA configuration if you have this as goal:&lt;/P&gt;&lt;P&gt;&lt;A href="http://support.sas.com/documentation/cdl/en/bisecag/67045/HTML/default/viewer.htm#n1d1zo1jsf2o0en1ehu4c4simfky.htm" title="http://support.sas.com/documentation/cdl/en/bisecag/67045/HTML/default/viewer.htm#n1d1zo1jsf2o0en1ehu4c4simfky.htm"&gt;SAS(R) 9.4 Intelligence Platform: Security Administration Guide, Second Edition&lt;/A&gt;&lt;/P&gt;&lt;P&gt;SAS portal access and EGuide are complete different ways in that.&amp;nbsp; &lt;/P&gt;&lt;P&gt;SAS portal is often set up with a shared account and hard code password on the OS. Traceabilty auditability is solved different eg by closing functionality with fixed menus&lt;/P&gt;&lt;P&gt;SAS Eguide is commonly running by a personal key as needed to be traceable/auditble with all analytics freedom&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 01 May 2014 06:06:07 GMT</pubDate>
    <dc:creator>jakarman</dc:creator>
    <dc:date>2014-05-01T06:06:07Z</dc:date>
    <item>
      <title>Enterprise Guide and Windows Authentication</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Enterprise-Guide-and-Windows-Authentication/m-p/140065#M1603</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Why does EG keep asking users to enter their passwords even when using Windows Authentication.?&lt;/P&gt;&lt;P&gt;The SAS Portal seems to work fine with Windows Authentication.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 May 2014 02:59:53 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Enterprise-Guide-and-Windows-Authentication/m-p/140065#M1603</guid>
      <dc:creator>Jaime</dc:creator>
      <dc:date>2014-05-01T02:59:53Z</dc:date>
    </item>
    <item>
      <title>Re: Enterprise Guide and Windows Authentication</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Enterprise-Guide-and-Windows-Authentication/m-p/140066#M1604</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Check the IWA configuration if you have this as goal:&lt;/P&gt;&lt;P&gt;&lt;A href="http://support.sas.com/documentation/cdl/en/bisecag/67045/HTML/default/viewer.htm#n1d1zo1jsf2o0en1ehu4c4simfky.htm" title="http://support.sas.com/documentation/cdl/en/bisecag/67045/HTML/default/viewer.htm#n1d1zo1jsf2o0en1ehu4c4simfky.htm"&gt;SAS(R) 9.4 Intelligence Platform: Security Administration Guide, Second Edition&lt;/A&gt;&lt;/P&gt;&lt;P&gt;SAS portal access and EGuide are complete different ways in that.&amp;nbsp; &lt;/P&gt;&lt;P&gt;SAS portal is often set up with a shared account and hard code password on the OS. Traceabilty auditability is solved different eg by closing functionality with fixed menus&lt;/P&gt;&lt;P&gt;SAS Eguide is commonly running by a personal key as needed to be traceable/auditble with all analytics freedom&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 May 2014 06:06:07 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Enterprise-Guide-and-Windows-Authentication/m-p/140066#M1604</guid>
      <dc:creator>jakarman</dc:creator>
      <dc:date>2014-05-01T06:06:07Z</dc:date>
    </item>
  </channel>
</rss>

