Note: This is not a universally necessary task. This is one of several solutions to a mixed provider situation. See Mixed Providers.
Log on to SAS Management Console as someone who has user administration capabilities (for example, sasadm@saspw).
On the Plug-ins tab, expand Server Manager, the application server (for example, SASApp) and the logical server (for example, SASApp - Logical Workspace Server).
(Optional) Right-click the logical server, select Properties, and select the Options tab. Make sure that the Authentication service is set to use Host with Username/Password. Click OK to close the dialog box and return to Server Manager.
Below the logical server , select the server (for example, SASApp - Workspace Server).
In the display panel, right-click the server's connection object and select Properties.
On the Options tab, notice the value in the Authentication domain drop-down list. If the value is something other than DefaultAuth, proceed to step 6. Otherwise, complete these steps:
Next to the Authentication domain drop-down list, click New.
In the New Authentication Domain dialog box, enter a name such as UNIXAuth or WorkspaceAuth (you can use any name that is meaningful to you). Click OK.
On the Options tab, make sure the new authentication domain is selected in the Authentication domain drop-down list. Click OK.
Create a SAS copy of credentials that are known to the workspace server's host operating system. In most cases, you will store shared credentials on a group's Accounts. You can also store a unique set of individual credentials on each user's Accounts tab. Each login must be assigned to the workspace server's authentication domain. Each login must include both a user ID and a password.
For example, for a workspace server on UNIX:
For example, for a workspace server on Windows:
If you store credentials for a workspace server that runs on Windows, give users the Log on as a batch job privilege. See Windows Privileges.
Note: If you don't store the passwords, users are prompted for such credentials when they make a request that requires access to the workspace server. Only desktop applications and SAS Web Report Studio provide such secondary logon prompts.
Note: Do not instead leave the workspace server in DefaultAuth and move inbound logins to some other authentication domain. Failure to follow this recommendation won't affect the initial logon process, but it will interfere with access to the workspace server. By default, all clients insert the credentials that a user submits at the logon prompt into that user's context as a DefaultAuth entry. This cached DefaultAuth entry has priority over any DefaultAuth credentials that are retrieved from logins in the metadata.