<?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 Authorization Domains in Developers</title>
    <link>https://communities.sas.com/t5/Developers/Authorization-Domains/m-p/70743#M3377</link>
    <description>We are installing SAS on two computers. One computer holds the meta data server and is in the DefaultAuth Authorization Domain. &lt;BR /&gt;
&lt;BR /&gt;
The username/password for the second server application is in a LinuxAuth domain.&lt;BR /&gt;
&lt;BR /&gt;
I've been looking through the 5-6 manuals on the subject, but I can find any place where the Autorization Domain is tied to a specific application server. I was expecting to see an application server tied to an autorization domain. Currently it looks like EG is authorizing against the host rather than the Authorization Domain.

Message was edited by: varronr</description>
    <pubDate>Fri, 11 Sep 2009 13:58:21 GMT</pubDate>
    <dc:creator>deleted_user</dc:creator>
    <dc:date>2009-09-11T13:58:21Z</dc:date>
    <item>
      <title>Authorization Domains</title>
      <link>https://communities.sas.com/t5/Developers/Authorization-Domains/m-p/70743#M3377</link>
      <description>We are installing SAS on two computers. One computer holds the meta data server and is in the DefaultAuth Authorization Domain. &lt;BR /&gt;
&lt;BR /&gt;
The username/password for the second server application is in a LinuxAuth domain.&lt;BR /&gt;
&lt;BR /&gt;
I've been looking through the 5-6 manuals on the subject, but I can find any place where the Autorization Domain is tied to a specific application server. I was expecting to see an application server tied to an autorization domain. Currently it looks like EG is authorizing against the host rather than the Authorization Domain.

Message was edited by: varronr</description>
      <pubDate>Fri, 11 Sep 2009 13:58:21 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Developers/Authorization-Domains/m-p/70743#M3377</guid>
      <dc:creator>deleted_user</dc:creator>
      <dc:date>2009-09-11T13:58:21Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization Domains</title>
      <link>https://communities.sas.com/t5/Developers/Authorization-Domains/m-p/70744#M3378</link>
      <description>I asked someone about this, and here is the information they provided:&lt;BR /&gt;
&lt;BR /&gt;
You must set the authentication domain on the individual servers and spawners using the SAS Management Console Server Manager plug-in. For example, for a Workspace server, navigate to:&lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;SASApp &amp;gt; SASApp Logical Workspace Server &amp;gt; SASApp - Workspace Server&lt;/B&gt;&lt;BR /&gt;
&lt;BR /&gt;
In the right-hand pane, right-click on the connection and then select &lt;B&gt;Properties&lt;/B&gt;.  On the &lt;B&gt;Options&lt;/B&gt; tab you will see a selection box for the authentication domain.  The process is similar for a Stored Process server, but you will need to set the authentication domain for the connection and any load-balanced connections.&lt;BR /&gt;
&lt;BR /&gt;
For the object spawner, select the spawner in the Server Manager plug-in, right-click on the operator connection, and then select &lt;B&gt;Properties&lt;/B&gt;.  The authentication domain can be set on the &lt;B&gt;Options&lt;/B&gt; tab.  Repeat the process for the port bank connections.&lt;BR /&gt;
&lt;BR /&gt;
Vince DelGobbo&lt;BR /&gt;
SAS R&amp;amp;D</description>
      <pubDate>Fri, 11 Sep 2009 16:43:23 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Developers/Authorization-Domains/m-p/70744#M3378</guid>
      <dc:creator>Vince_SAS</dc:creator>
      <dc:date>2009-09-11T16:43:23Z</dc:date>
    </item>
  </channel>
</rss>

