A registered user who has a connection to the metadata
server accesses the OLAP server, stored process server, and pooled
workspace server seamlessly by SAS token authentication. Authentication
to following servers requires coordination:
standard workspace server
To provide seamless
access, coordinate the workspace server with the metadata server.
third-party data server (for example, Oracle)
To provide access,
select an approach from the following table.
Authentication to a Third-Party Data Server
|
|
|
Provide seamless access
and preserve individual identity to the target server.
|
Store individual user
IDs and passwords in the metadata (each on the Accounts tab of a different user definition).
|
|
|
Store the user ID and
password for one shared account in the metadata (on the Accounts tab of a group definition).
|
Provide seamless access
with a few distinct access levels for resources in the target server.
|
Store a few shared user
IDs and passwords in the metadata (each in the Accounts area of a different group definition). Or, for a hybrid approach,
use a combination of personal and group logins.
|
Preserve individual
identity.
|
No configuration is
required. Users will be prompted for credentials for the target server.
Secondary prompting is supported for desktop applications and SAS
Web Report Studio.
|
Note: In general, requesting users
can access only those servers for which they have the ReadMetadata
permission. An exception is client-side pooling, in which access depends
on membership in a puddle group.
Note: This topic is about metadata-aware
connections. Direct connections to a SAS server can't use SAS token
authentication. Direct connections use client-supplied credentials
or, in some cases, Integrated Windows authentication.