07.08.2013 Views

SAS 9.1.3 Intelligence Platform: System Administration Guide

SAS 9.1.3 Intelligence Platform: System Administration Guide

SAS 9.1.3 Intelligence Platform: System Administration Guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

18 About Required User and Group Metadata Objects R Chapter 2<br />

About Required User and Group Metadata Objects<br />

At the end of the installation process, certain metadata objects must exist in your<br />

metadata repository. This section lists the User and Group objects that must have been<br />

defined in the metadata in order for your servers and applications to work correctly.<br />

You can use the User Manager plug-in for <strong>SAS</strong> Management Console to verify that<br />

these objects have been created properly.<br />

Table 2.1 Summary of Metadata Identities<br />

Metadata Identity User ID* Password** Authentication<br />

Domain<br />

User: <strong>SAS</strong><br />

Administrator<br />

User: <strong>SAS</strong> Trusted<br />

User<br />

sasadm (not stored)<br />

Group Membership<br />

Information<br />

sastrust (not stored) member of: <strong>SAS</strong><br />

<strong>System</strong> Services<br />

group, <strong>SAS</strong> General<br />

Servers group<br />

User: <strong>SAS</strong> Guest sasguest ******** DefaultAuth<br />

User: <strong>SAS</strong> Demo User sasdemo ******** DefaultAuth member of: Portal<br />

Demos<br />

User: <strong>SAS</strong> Web<br />

Administrator***<br />

Group: <strong>SAS</strong> <strong>System</strong><br />

Services<br />

Group: <strong>SAS</strong> General<br />

Servers<br />

Group: Portal<br />

Admins***<br />

Group: Portal<br />

Demos***<br />

Group: WRS<br />

Administrator****<br />

Group: WRS Report<br />

Author****<br />

Group: WRS Advanced<br />

User****<br />

saswbadm ******** DefaultAuth member of: Portal<br />

Admins group, <strong>SAS</strong><br />

<strong>System</strong> Services group<br />

members: <strong>SAS</strong><br />

Trusted User, <strong>SAS</strong><br />

Web Administrator<br />

sassrv ******** DefaultAuth members: <strong>SAS</strong><br />

Trusted User<br />

members: <strong>SAS</strong> Web<br />

Administrator<br />

members: <strong>SAS</strong> Demo<br />

User<br />

* These are the recommended IDs. They should correspond to accounts in your authentication<br />

provider. On Windows, the user ID in the login should be fully qualified with a host or domain<br />

name (for example, host-name\sasadm).<br />

** If you are logged on to <strong>SAS</strong> Management Console as an unrestricted user, you will always see<br />

******** in the password column, even if no password was specified.<br />

***You only need this metadata identity if you are running the <strong>SAS</strong> Information Delivery Portal.<br />

****You only need this metadata identity if you are running <strong>SAS</strong> Web Report Studio.<br />

For more information about why the <strong>SAS</strong> General Servers group must be set up this<br />

way, and about the problems you will see if it is not set up this way, see “Overview of

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!