WAS v8.5 > Develop applications > Develop web services - Security (WS-Security) > Configure Web Services Security during application assembly > Configure XML basic authentication for v5.x web services with an assembly tool

Configure the server to handle basic authentication information

Basic authentication (BasicAuth) refers to the user ID and the password of a valid user in the registry of the target server. After a request is received containing basic authentication information, the server needs to log in to form a credential. The credential is used for authorization.

There is an important distinction between v5.x and v6.0.x and later applications. The information in this article supports v5.x applications only used with WebSphere Application Server v6.0.x and later. The information does not apply to v6.0.x and later applications.

Complete the following steps to configure the server to handle BasicAuth authentication information:

  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 EJB Projects > application_name > ejbModule > META-INF.
  4. Right-click the webservices.xml file, and click Open with > Web services editor.

  5. Click the Extensions tab, located at the bottom of the web services editor within an assembly tool.

  6. Expand the Request receiver service configuration details > Login configuration section. We can select the following options:

    • BasicAuth
    • Signature
    • ID assertion
    • Lightweight Third Party Authentication (LTPA)

  7. Select BasicAuth to authenticate the client with a user ID and a password. The client must specify a valid user ID and password in the server user registry. If the user ID and the password supplied are not valid, an exception is provided, and the request ends without invoking the resource.

    We can select multiple login configurations, which means that different types of security information might be received at the server. The order in which the login configurations are added decides the order in which they are processed when a request is received. Problems can occur if we have multiple login configurations added that have security tokens in common. For example, ID assertion contains a BasicAuth token. For ID assertion to work properly, list ID assertion ahead of BasicAuth in the processing list or the BasicAuth processing overrides the IDAssertion processing.

After we specify how the server handles BasicAuth authentication information, specify how the server validates the authentication information. See the task for configuring the server to validate BasicAuth authentication if we have not previously specified this information.


Related concepts:

BasicAuth authentication method
Development and assembly tools


Related


Configure the server to validate basic authentication information
Configure the server security bindings using an assembly tool
Configure the server security bindings


+

Search Tips   |   Advanced Search