Basic authentication (BasicAuth) refers to the user ID and password
of a valid user in the registry of the target server. BasicAuth information
can be collected in many ways, including through an administrative console
prompt, a standard in (Stdin) prompt, or specified in the bindings that prevents
user interaction.
Before you begin
Important: There is an important distinction between Version
5.x and Version 6.0.x and later applications. The information
in this article supports Version 5.x applications only that are used
with WebSphere Application Server Version 6.0.x and later. The information
does not apply to Version 6.0.x and later applications.
For
more information on BasicAuth authentication, see: BasicAuth authentication method
.
About this task
Attention: WebSphere Application Server supports nonce
(randomly generated token) with BasicAuth authentication. For more information,
see
Nonce.
Complete
the following steps to specify BasicAuth as the authentication method:
Procedure
- Launch an assembly tool. For more information on the
assembly tools, see Assembly tools
.
- Switch to the Java 2 Platform, Enterprise Edition (J2EE) perspective.
Click Window > Open Perspective > J2EE.
- Click Application Client Projects > application_name >
appClientModule > META-INF.
- Right-click the application-client.xml file, select Open
with > Deployment descriptor editor.
- Click the WS Extensions tab, which is located at the bottom of
the deployment descriptor editor within the assembly tool.
- Expand the Request sender configuration > Login configuration section.
The only valid login configuration choices for a pure client are BasicAuth
and Signature.
- Select BasicAuth to authenticate the client using a user
ID and a password. This user ID and password must be specified
in the target user registry. The other choice, Signature, attempts to authenticate
the client using the certificate used to digitally sign the message.