+

Search Tips   |   Advanced Search

 

Example: Using the default single sign-on token

 

Do not use the default single sign-on token in service provider code. This default token is used by the WAS run-time code only.

Size limitations exist for this token when it is added as an HTTP cookie. If create an HTTP cookie using this token framework, you can implement a custom single sign-on token. To implement a custom single sign-on token see Implementing a custom single sign-on token for more information.

 

Change the token factory that is associated with the default single sign-on token

When the default single sign-on token is generated, the appserver utilizes the TokenFactory class that is specified using the com.ibm.wsspi.security.token.singleSignonTokenFactory property. To modify this property using the console...

  1. Click Security > Secure administration, applications, and infrastructure.

  2. Under Authentication, click Custom properties.

The com.ibm.ws.security.ltpa.LTPAToken2Factory token factory is the default that is specified for this property. This token factory creates a single sign-on (SSO) token called LtpaToken2, which WAS uses for propagation. This token factory uses the AES/CBC/PKCS5Padding cipher. If you change this token factory, you lose the interoperability with any servers running a version of WAS prior to version 5.1.1 that use the default token factory. Only servers running WebSphere Application Server V5.1.1 or later with propagation enabled are aware of the LtpaToken2 cookie. If all of your appservers use WAS V5.1.1 or later and all of your servers use your new token factory this awareness is not a problem. If perform your own signing and encryption of the default single sign-on token, implement the following classes:

Your token factory implementation instantiates (createToken) and validates (validateTokenBytes) your token implementation. You can use the Lightweight Third-Party Authentication (LTPA) keys passed into the initialize method of the token factory or you can use your own keys. If you use your own keys, they must be the same everywhere to validate the tokens that are generated using those keys. See the API documentation, available through a link on the front page of the information center, for more information on implementing your own custom token factory. To associate your token factory with the default single sign-on token using the console, complete the following steps:

  1. Click Security > Secure administration, applications, and infrastructure.

  2. Under Authentication, click Custom properties.

  3. Locate the com.ibm.wsspi.security.token.singleSignonTokenFactory property and verify that the value of this property matches your custom TokenFactory implementation.

  4. Verify that your implementation classes are put into the app_server_root/classes directory so that the class loader can load the classes.

  5. Verify that your implementation classes are located in the ${USER_INSTALL_ROOT}/classes directory so that the class loader can load the classes.




 

Related concepts


Security attribute propagation

 

Related tasks


Propagating security attributes among appservers
Implementing a custom single sign-on token

 

Reference topic