IBM WebSphere V5.0 Security - CGISecurity

– Container-managed Authentication Alias: select an authentication alias
entry for this field. If no alias is available, you need to create one.
If this authentication fails, JMS Connections will not be created.
4. Save the configuration.
7.2.4 Security for WebSphere MQ (external provider)
This section will briefly describe how to manage security using an external
messaging provider, in this case WebSphere MQ.
Use the Administrative Console of WebSphere Application Server for this
configuration.
1. Navigate to Resources -> WebSphere MQ JMS Provider, click the
Additional Properties.
Here you can configure JMS Queue Connection Factories and also Queue
Destinations.
2. Select the scope for the configuration, in our case: server, then click Apply.
3. Click MQSeries Queue Connection Factories.
4. On the next page, click New. Similarly to the Embedded JMS provider, specify
the following fields beside the other non-security related fields:
– Component-managed Authentication Alias: select an authentication alias
entry for this field. If no alias is available, you need to create one.
– Container-managed Authentication Alias: select an authentication alias
entry for this field. If no alias is available, you need to create one.
Important: The user name and password specified here depend on the type
of global security. Specify the OS user name and password when LocalOS is
used as user registry; use an LDAP user name and password when using
LDAP as user registry.
5. Click Apply.
6. Go back to WebSphere MQ JMS Provider and click WebSphere MQ Queue
Destinations.
7. Click New which opens a new page, and define the fields for the new queue
destination.
8. Save the configuration.
Each time a connection factory is created, it first gets authenticated by the
security information we have provided.
166 IBM WebSphere V5.0 Security Handbook