A00-250 practice question 7 of 15
A platform administrator has converted the standard workspace server to use SAS Token Authentication in a mixed provider environment. What will be the outcome of this conversion?
Full set: 65 questionsConverting a standard workspace server to use SAS Token Authentication is a key step in configuring single sign-on (SSO) for SAS client applications like SAS Enterprise Guide. In a mixed provider environment, a user might authenticate initially through a web mechanism (e.g., IWA, SAML). The SAS Logon Manager then issues a security token. This token can be used by the client application to connect to the workspace server without requiring the user to re-enter their credentials. This process provides a "seamless" access experience, bridging the different authentication methods used by web and client/server components.
A. Credential caching will be used to provide access. Token authentication uses a temporary, generated token for access, which is distinct from caching the user's primary credentials (e.g., password).
B. Windows and Unix servers will have aligned authentication providers. This change does not align the underlying OS-level authentication providers (e.g., Active Directory and PAM); it provides a common SAS-level authentication layer on top of them.
C. Host access by individual accounts will be provided. The standard workspace server already provides host access via individual accounts. This is a fundamental behavior, not a new outcome of converting to token authentication.
1. SAS® 9.4 Intelligence Platform: Security Administration Guide, Second Edition.
Page 41, Chapter 3, "How SAS Token Authentication Works": "SAS token authentication enables single sign-on for desktop applications such as SAS Enterprise Guide and SAS Add-In for Microsoft Office. After a user signs on to one of these applications, the user can access SAS servers without re-entering a user ID and password." This directly supports the concept of seamless access.
2. SAS® 9.4 Intelligence Platform: Overview, Second Edition.
Page 26, Chapter 2, "Authentication": The document reiterates the function of token authentication: "SAS token authentication enables single sign-on for desktop applications... This feature provides a more seamless logon experience for users." This explicitly uses the term "seamless" to describe the outcome.
3. SAS Institute Inc., "Paper 332-2013: A Guide to SAS® 9.4 Security and Authentication." SAS Global Forum 2013.
Page 4, "SAS Token Authentication": "The primary purpose of SAS token authentication is to provide single sign-on (SSO) for rich client applications... This provides a seamless experience for the end user." This peer-reviewed conference paper confirms that the goal and outcome is a seamless user experience.
Keep practicing
Take the free A00-250 practice test
Ten exam-style questions with answers and explanations, plus the exam facts and study guides.
More questions
Other A00-250 practice questions
- Question 1A platform administrator needs to restore backup files to a running metadata server. Whic…
- Question 2How many object spawners, at a minimum, need to be defined in the metadata?
- Question 3The passwords for service accounts that occur in some of the configuration files have bee…
- Question 4A platform administrator needs to associate a library with an application server. What pe…
- Question 5What is the correct order in which to start up the SAS servers and spawners?
- Question 6An internal account is used to provide the initial connection to which server?
