+

Search Tips   |   Advanced Search

Configure the client for identity assertion: specifying the method

We can configure identity assertion authentication. The purpose of identity assertion is to assert the authenticated identity of the originating client from a web service to a downstream web service.

This task is used to configure identity assertion authentication. The purpose of identity assertion is to assert the authenticated identity of the originating client from a web service to a downstream web service. Do not attempt to configure identity assertion from a pure client. Identity assertion works only when we configure on the client-side of a web service acting as a client to a downstream web service.

In order for the downstream web service to accept the identity of the originating client (just the user name), supply a special trusted BasicAuth credential that the downstream web service trusts and can authenticate successfully. Specify the user ID of the special BasicAuth credential in a trusted ID evaluator on the downstream web service configuration. See topics about trusted ID evaluators.

Complete the following steps to specify identity assertion as the authentication method:


Tasks

  1. Launch an assembly tool. For more information, see the related information on Assembly Tools.
  2. Switch to the Java EE perspective. Click Window > Open Perspective > J2EE.

  3. Click Application Client Projects > application_name > appClientModule > META-INF.
  4. Right-click the application-client.xml file, select Open with > Deployment descriptor editor.

  5. Click the WS Extension tab, which is located at the end of the deployment descriptor editor within the assembly tool.

  6. Expand the Request sender configuration > Login configuration section.

  7. Select IDAssertion as the authentication method. For more conceptual information on identity assertion authentication, see Identity assertion in a SOAP message.

  8. Expand the IDAssertion section.

  9. For the ID type, select Username. This value works with all registry types and originating authentication methods.

  10. For the trust mode, select either BasicAuth or Signature.

    • By selecting BasicAuth, we must include basic authentication information (user ID and password), which the downstream web service has specified in the trusted ID evaluator as a trusted user ID. See Configure the client for signature authentication: collecting the authentication information to specify the user ID and password information.
    • By selecting Signature the certificate configured in the signature information section used to sign the data also is used as the trusted subject. The Signature is used to create a credential and user ID, which the certificate mapped to the downstream registry, is used in the trusted ID evaluator as a trusted user ID.


What to do next

See Configure the client security bindings using an assembly tool for more information on the web services client editor within the assembly tool.

After we specify identity assertion as the authentication method used by the client, specify how to collect the authentication information. See Configure the client for identity assertion: collecting the authentication method for more information.


Related:

  • Trusted ID evaluator
  • Identity assertion in a SOAP message
  • Development and assembly tools
  • Configure the client for identity assertion: collecting the authentication method
  • Configure the client security bindings using an assembly tool