[Version 6 only]WebSphere Application Server - Express, Version 6.0.x     Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Configuring the caller in consumer security constraints

Before you begin

Prior to completing this task, you must import your application into an assembly tool. For information on how to import your application, see Importing enterprise applications.

Why and when to perform this task

The caller is used to identify the token. The run time for Web services security uses this token identity to create the security credential and principal for WebSphere Application Server. The token identity must be in the configured user registry so that the Application Server can use the token identity in Java 2 Platform, Enterprise Edition (J2EE) authorization checks.

Complete the following steps to specify the caller part when you configure the consumer security constraints for either the response consumer or the request consumer. The response consumer is configured for the client and the request consumer is configured for the server. In the following steps, you must configure either the client-side extensions in step 2 or the server-side extensions in step 3.

Steps for this task

  1. Start the assembly tool and click Window > Open Perspective > J2EE.
  2. Optional: Locate the client-side extensions using the Project Explorer window. The Client Deployment Descriptor window is displayed. This Web service contains the extensions that you need to configure. Complete the following steps to locate the client-side extensions:
    1. Expand the Web Services > Client section and double-click the name of the Web service.
    2. Click the WS Extension tab and expand the Response Consumer Configuration section.
  3. Optional: Locate the server-side extensions using the Project Explorer window. The Web Services Editor window is displayed. This Web service contains the extensions that you need to configure. Complete the following steps to locate the server-side extensions:
    1. Expand the Web Services > Services section and double-click the name of the Web service.
    2. Click the Extensions tab and expand the Request Consumer Service Configuration Details section.
  4. Expand the Caller Part section.
  5. Click Add to specify the caller part. The Caller Part Dialog window is displayed. Complete the following steps to configure the caller part:
    1. Specify the name of the caller in the Name field.
    2. Optional: Specify the name of an integrity or confidentiality part in the Required Integrity or Required Confidentiality part field if you want to select the token that used for either digital signature or encryption as the caller token. For more information on these configurations, see the following tasks:
      Important: Either complete this step or specify a token type in the Token type field in the next step.
    3. Optional: Specify a token type in the Token type field if you want to select a stand-alone security token as the caller token.

      If a stand-alone security token is used for authentication, then the Uniform Resource Identifier (URI) and local name attributes must define the type of security token that is used for authentication. You can select standard or custom security tokens by URI and local name.

      If you specify a token type in the Token type field, complete the following steps:
      1. Specify the namespace URI of the security token that is used for authentication in the URI field.
      2. Specify the local name of the security token that is used for authentication in the Local name field. The following table shows the URI and local name combinations that are supported:
        Table 1. URI and Local name combinations
        URI Local name
        X.509 certificate token http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3
        X.509 certificates in a PKIPath http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509PKIPathv1
        A list of X509 certificates and CRLs in a PKCS#7 http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#PKCS7
        http://www.ibm.com/websphere/appserver/tokentype/5.0.2 LTPA

        The Custom token requires that you specify both the URI and the Local name.

  6. Optional: Configure identity assertion. For more information, see Configuring identity assertion
  7. Optional: Click Add and specify a Trust method property in the Trust method property section, if necessary.
  8. Optional: Click Add and specify an additional property in the Property section, if necessary.
  9. Click OK to save the configuration changes.
    Note: These configurations on the consumer side and the generator side must match.



Related tasks
Signing message elements in consumer security constraints with keywords
Signing message elements in consumer security constraints with an XPath expression
Encrypting message elements in consumer security constraints with keywords
Encrypting message elements in consumer security constraints with an XPath expression
Configuring identity assertion

Task topic    

Terms of Use | Feedback

Last updated: Jun 8, 2005 12:45:23 PM EDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.express.doc/info/exp/ae/twbs_speccallerconsbind.html

© Copyright IBM Corporation 2004, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)