create, locate, maintain, and aggregate information about users of the SAS Foundation Services.
store and retrieve User Context objects for sharing between applications. The User Context contains the user's active repository connections, identities, and profile.
manage and access user profiles. A profile is a collection of name/value pairs that specify preferences and configuration or initialization data for a user for a particular application.
access group profiles. A group profile specifies preferences and configuration or initialization data for a group of users for a particular application.

For more information, see com.sas.services.user in the Foundation Services class documentation.

The User Service utilizes a user context to hold the user's information for connections, identities, and profile. The profile then contains application profile data for the user. The User Service configuration consists of the following:

Users: the user definition specifies the credentials that are associated with this User Service. The user definition consists of the user ID, password, and authentication domain of the user.
Profiles: the profile definition contains a collection of name/value pairs that specify preferences and initialization data for a user of an application. The profile definition contains the name of the associated application, where the profile is located, the class and type of the profile, and a filter used to locate the profile.

To configure the User Service configuration:

In the SAS Management Console navigation tree, expand the Foundation Services Manager tree to locate and select the User Service you wish to modify. Right-click the User Service and select Properties from the pop-up menu. The User Service properties window appears.
Select the Service Configuration tab. Click Edit Configuration. The User Service Configuration window appears.
On the General tab, to add authentication domain or base LDAP information, enter the following information:

Name

specifies the default authentication domain name. If an entry for a user does not supply an authentication domain, this authentication domain name is used.

People

specifies the distinguished name (DN) for the context in LDAP that contains user metadata.

Groups

specifies the distinguished name (DN) for the context in LDAP that contains group metadata.

Credentials

specifies the location in LDAP that contains credential information.
On the Users tab, and click Add to add a user, or select a user and click Edit to edit a user. Enter the following information:

ID

specifies the user ID (for the SAS Metadata Server) or LDAP directory entry (for LDAP) of the user.

Password

specifies the password needed for the user to log on to the specified authentication domain.

Confirm Password

confirms the password that you specified in the Password field.

Domain

specifies the authentication domain for which the user ID is valid.

Click OK to return to the User Service Configuration window.
On the Profiles tab, click Add to add a profile, or select a profile and click Edit to edit a profile. Enter the following information:

Application

specifies the application whose profile is specified.

Domain URL

specifies the location of the repository where the application profile is stored.

Class

specifies the class associated with the profile.

Type

specifies the profile type. If you are NOT using a custom profile class, leave this field blank.

Filter

specifies information to help locate the correct profile. If you are NOT using a custom profile class, leave this field blank.

Click OK to return to the User Service Configuration window.
When you are finished adding User Service configuration information, click OK to save the User Service configuration to a metadata repository.

Understanding and Editing the Session Service

The Session Service enables applications to:

create a session context. A session context is a control structure that maintains state information within a bound session, facilitating resource management and context passing.
bind objects to a session context.
use the session context as a convenience container for passing multiple contexts.
use the session context as a convenience container for passing other services, such as User Services and Logging Services.
notify bound objects when they are removed from the session context or when the session context is destroyed, so that objects can perform any necessary cleanup.

For more information, see com.sas.services.session in the Foundation Services class documentation.

When the Session Service initializes, it discovers the Logging Service, and obtains a default logging context. The Session Service then uses the Session Service configuration to determine whether to bind to a user context when creating the root session context:

If the Session Service deployment configuration specifies a user context name, the Session Service discovers the User Service and obtains the default user context. The Session Service then creates a default root session context that is bound to this default user context.
If the Session Service deployment configuration does not specify a user context name, the Session Service creates a default root session context that is not bound to any user context.

Applications can then use the root session context to track shared resources that are global to the application and to obtain the initialized logging context and default user context (if one was specified).

To configure a default user context name in the Session Service configuration:

In the SAS Management Console navigation tree, expand the Foundation Services Manager tree to locate and select the Session Service that you want to modify. Right-click the Session Service and select Properties from the pop-up menu. The Session Service properties window appears.
Select the Service Configuration tab and click Edit Configuration. The Session Service Configuration window appears.
Specify the default User Context Name. Click OK to return to the Session Service Configuration window.
Click OK to save the Session Service configuration to the metadata repository.