Add a User

  1. In the Users Module, click the create icon and select New User.
  2. On the New User window, enter a name and optional display name. Then click Save. The new user object opens on the Basic Properties page.
  3. From the drop-down menu, select Accounts. On the Accounts page, click the plus icon to add a login.
    • In the Domain column, select DefaultAuth.
    • In the Stored User ID column, enter the user's external account ID. 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\myID or myID@mycompany.com).
    If your site uses web authentication, refer to the following table for adapted instructions:
    Adapted Instructions for Sites That Use Web Authentication
    Type of User
    Adapted Instructions1
    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, you do not need to follow these adapted instructions.
  4. (Optional) From the drop-down menu, select Member of. On the Member of page, click the edit icon to make a user a direct member of one or more groups and roles.
    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).
  5. (Optional) To provide seamless access to a third-party server such as a DBMS, either give the user a second login or make the user a member of a group that has a shared login for the third-party server.
  6. Save the new user.
Note: Do not use the settings in any of the Authorization: pages to modify authorizations for a user. The settings in this window have no effect on what the user can do. They affect the permissions for the user object itself.
Note: If the user accesses a standard workspace server with Windows host credentials, make sure the user has the "Log on as a batch job" Windows privilege on that host. The user's Windows account should be a member of a Windows group that is named SAS Server Users or something similar.