IBM WebSphere V5.0 Security - CGISecurity

– Container-managed Authentication Alias: select an authentication aliasentry 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 externalmessaging provider, in this case WebSphere MQ.Use the Administrative Console of WebSphere Application Server for thisconfiguration.1. Navigate to Resources -> WebSphere MQ JMS Provider, click theAdditional Properties.Here you can configure JMS Queue Connection Factories and also QueueDestinations.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, specifythe following fields beside the other non-security related fields:– Component-managed Authentication Alias: select an authentication aliasentry for this field. If no alias is available, you need to create one.– Container-managed Authentication Alias: select an authentication aliasentry for this field. If no alias is available, you need to create one.Important: The user name and password specified here depend on the typeof global security. Specify the OS user name and password when LocalOS isused as user registry; use an LDAP user name and password when usingLDAP as user registry.5. Click Apply.6. Go back to WebSphere MQ JMS Provider and click WebSphere MQ QueueDestinations.7. Click New which opens a new page, and define the fields for the new queuedestination.8. Save the configuration.Each time a connection factory is created, it first gets authenticated by thesecurity information we have provided.166 IBM WebSphere V5.0 Security Handbook