Configure the server to validate BasicAuth authentication information

 

Before you begin

Important distinction between V5.x and v6.x applications

Note: The information in this article supports v5.x applications only that are used with WAS v6.x. The information does not apply to v6.0.x applications.

BasicAuth refers to the user ID and the password of a valid user in the registry of the target server.  Once a request is received that contains basic authentication information, the server needs to log in to form a credential.  The credential is used for authorization. If the user ID and the password supplied is invalid, an exception is thrown and the request ends without invoking the resource. For more information on BasicAuth authentication, see BasicAuth authentication method.

 

Overview

Complete the following steps to specify how the server validates the BasicAuth authentication information:

 

Procedure

  1. Launch an assembly tool. For more information on the assembly tools, see Assembly tools.

  2. Open the J2EE perspective by clicking Window > Open perspective > Other > J2EE.

  3. Click EJB Projects > appname > ejbModule > META-INF.

  4. Right-click the webservices.xml file, and click Open with > Web services editor.

  5. Click the Binding Configurations tab, which is located at the bottom of the Web services editor within an assembly tool such as the Application Server Toolkit or Rational Web Developer.

  6. Expand the Request receiver binding configuration details > Login mapping section.

  7. Click Edit to view the login mapping information or click Add to add new login mapping information. The login mapping dialog is displayed. Select or enter the following information:

    Authentication method

    Specifies the type of authentication that occurs. Select BasicAuth to use basic authentication.

    Configuration name

    Specifies the Java Authentication and Authorization Service (JAAS) login configuration name. For the BasicAuth authentication method, enter WSLogin for the JAAS login Configuration name.

    Use token valid type

    Determines if you want to specify a custom token type. For the default authentication method selections, you do not need to specify this option.

    Token value type URI and Token value type URI local name

    When you select BasicAuth, one cannot edit the token value type URI and local name values. Specifies custom authentication types. For BasicAuth authentication leave these fields blank.

    Callback handler factory class name

    Creates a JAAS CallbackHandler implementation that understands the following callbacks:

    • javax.security.auth.callback.NameCallback

    • javax.security.auth.callback.PasswordCallback

    • com.ibm.wsspi.wssecurity.auth.callback.BinaryTokenCallback

    • com.ibm.wsspi.wssecurity.auth.callback.XMLTokenReceiverCallback

    • com.ibm.wsspi.wssecurity.auth.callback.PropertyCallback

    Callback handler factory property name and Callback handler factory property value

    Specifies callback handler properties for custom callback handler factory implementations. You do not need to specify any properties for the default callback handler factory implementation. For BasicAuth, you do not need to enter any property values.

    Login mapping property name and Login mapping property value

    Specifies properties for a custom login mapping. For the default implementations including BasicAuth, leave these fields blank.

 

What to do next

You must specify how the server handles the BasicAuth authentication method. See Configuring the server to handle BasicAuth authentication information if you have not previously specified this information.

 

See Also


BasicAuth authentication method

 

Related Tasks


Configuring the server to handle BasicAuth authentication information
Configuring the server security bindings using an assembly tool
Configuring the server security bindings using the administrative console