To create an individual
SAS identity:
-
On the
Plug-ins tab, select
User Manager. Make sure that
you are in the foundation repository.
-
-
Right-click and select
New
User.
-
On the
General tab, enter a name.
Tip
We recommend that you avoid
using spaces or special characters in the name of a user, group, or
role that you create. Not all components support spaces and special
characters in identity names.
-
On the
Accounts tab, click
New. In the
New
Login dialog box, select
DefaultAuth and enter the user's external account ID.
Note: In the standard configuration,
you can use any account (LDAP, Active Directory, host, or other) that
is known to the metadata server's host.
Note: For a Windows account, qualify
the ID (for example,
WIN\user or
user@mycompany.com).
Adapted Instructions for Sites That Use Web Authentication
|
|
|
Someone who uses only
Web applications
|
Select the Web realm
authentication domain (such as web) instead
of DefaultAuth and enter the user's Web realm
ID.
|
Someone who uses both
Web and desktop applications
|
Complete the standard
instructions and also add a Web realm login.
|
| 1If the Web user IDs and
the metadata server user IDs are identical, and the Web applications
do not use a standard workspace server, it is not necessary to follow
these adapted instructions.
|
Tip
Do not include a password
in this login.
-
Click
OK to save the new login. Click
OK again to
save the new user.
-
(Optional) Use the
Groups and Roles tab to make a user a direct member
of another group or a role.
Note: The user automatically belongs
to PUBLIC (everyone who can access the metadata server) and SASUSERS
(those members of PUBLIC who have a well-formed user definition).
-
Make sure that anyone
who uses Windows host credentials to access a standard workspace server
has the "Log on as a batch job" Windows privilege. For example, you
might add the user's Windows account to a Windows group that is named
SAS Server Users.
-
If you need to provide
seamless access to a third-party server that uses proprietary authentication,
either give the user a second login or make the user a member of a
group that has a shared login for that server.
See Make a SAS Copy of DBMS Credentials.
Note: You do not have to make changes
on the user's
Authorization tab. This tab
has no effect on what the user can do.