Create a validation realm that allows the Identity Asserter to validate user credentials using session information received from SMSESSION cookies and X509 Client Certificates.
Note: The following procedure provides an overview of the steps required to create the required policy objects with appropriate parameter settings. For detailed procedural information, see the Policy Server Configuration Guide.
To configure the SiteMinder Identity Asserter validation realm
Specifies a unique name for the authentication scheme.
An X509 Client Cert authentication scheme, such as X509 Client Cert Template, to enable the Identity Asserter to validate X.509 Client Certificates.
The name of the server where WebLogic is installed.
Leave the default value unchanged.
Note: This authentication scheme only passes credentials to the Policy Server for verification. It does not redirect requests to an SSL credential collector. Therefore, the Policy Server does not use the values specified in the Server Name and Target fields.
Note: See the Authentication Schemes chapter in the SiteMinder Policy Server Configuration Guide for instructions on creating an authentication scheme.
The domain you created in step 3.
A unique name for the realmfor example, SiteMinder Identity Asserter Validation Realm.
An optional description for the realm.
The name of the SiteMinder Agent identity that you created for the SiteMinder Agent.
Enter the Agent name in the text box or click the lookup button (...) to select the Agent name from a list of configured Agent identities.
/smiavalidationrealm
The authentication scheme you created in Step 2.
This option must be disabled.
This option must be disabled.
Non-persistent.
Note: If the session timeouts are not disabled, the identity assertion process might fail and the native WebLogic security services might challenge the request.
Note: You do not need to configure any rules for the Identity Asserter validation realm.
To configure the SiteMinder Identity Asserter to handle only requests from users with valid SiteMinder session tickets or X.509 certificates (that is, not to challenge requests for credentials), verify that the ChallengeForCredentials Agent configuration parameter is disabled by setting it to NO in the associated Agent Configuration Object or Agent configuration file.
For example:
ChallengeforCredentials=NO
| Copyright © 2010 CA. All rights reserved. | Email CA about this topic |