Authentication Mechanisms |
Summary | The metadata server generates and validates a single-use identity token for each authentication event. This has the effect of causing participating SAS servers to accept users who are connected to the metadata server. |
Scope |
|
Benefits |
|
Limits |
|
Use | Optional for the workspace server, otherwise mandatory within its scope |
The following figure is an abstraction of how this mechanism works.
SAS Token Authentication
The numbers in the figure correspond to these actions:Over the user's existing connection to the metadata server, the client requests an identity token for the target server. This step is initiated by a user request that requires access to the target server (for example, by a request in SAS Enterprise Guide for a cube that is associated with the OLAP server).
The metadata server generates the token and sends it to the client.
The client provides the token to the target server.
The target server sends the token to the metadata server for validation.
The metadata server validates the token and returns an acceptance message and a representation of the user to the target server.
The target server accepts the connection.
For instructions, see How to Configure SAS Token Authentication.
Copyright © 2011 by SAS Institute Inc., Cary, NC, USA. All rights reserved.