Configuring a Basic Authentication Identity for the Broker User Interface Component
To a Broker Server, the Broker user interface component is a just another client (for example, a Java program) requesting an authenticated connection. Thus, you assign a basic authentication identity to the Broker user interface and connect to a basic authentication enabled server as you would with any client. That allows the Broker Server to authenticate the Broker user interface at connection time.
Establishing a basic authentication identity for the Broker user interface and connecting to the basic authentication enabled Broker Server is a requirement for enabling Broker security.
The same Broker user interface component can connect to different Broker Servers. To connect to each Broker Server, the Broker user interface component must have a unique basic authentication identity associated with each Broker Server. For example, if your Broker user interface component in My webMethods requires to connect to five different Broker Servers, you must configure five different basic authentication identities in My webMethods.
Once the identity of Broker user interface component in My webMethods to connect to a Broker Server is saved in the database, that identity is used to authenticate every user session. You can use the following procedure to set a basic authentication identity for Broker user interface component in My webMethods to connect to a Broker Server.
To assign a basic authentication identity to the
Broker user interface component
1. In My webMethods: Messaging > Settings > Broker Administrator Identity
2. Select the server to which you want to connect.
Tip:
If there are several servers, to search for the required server, enter the name of the server in Server Name text field and click Search.
3. Click Change Identity.
4. In the Client Authentication dialog, select Username/Password from Client Authentication list box.
5. In the Username text field, type your basic authentication user name.
6. In the Password text field, type your basic authentication password.
7. Optionally, you can configure encryption.
a. Select the SSL Truststore.
The truststore you use for the Broker user interface must be located on the machine hosting your My webMethods applications.
b. Select the SSL truststore's File Type (certificate file format) from the SSL Truststore Type list.
c. Click the Yes option for Encryption.
8. Click Connect.
The identity details along with the encrypted password are stored in the database which My webMethods uses. Once the user establishes an identity, the identity details will be stored for new user sessions.