13.07.2015 Views

IBM WebSphere V5.0 Security - CGISecurity

IBM WebSphere V5.0 Security - CGISecurity

IBM WebSphere V5.0 Security - CGISecurity

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Example 7-9 Topic default permissions+pubKeeping the element empty signifies that this configuration is the defaulttopic configuration.7. To define permissions for a specific topic, we need to configure topic node inthe XML file as follows:Example 7-10 Topic permissionsITSOTopic+pubtuser01+pub+sub>8. Save and close the integral-jms-authorizations.xml file.<strong>Security</strong> for the <strong>WebSphere</strong> embedded JMS provider operates as part of<strong>WebSphere</strong> Application Server global security. This means that to enableEmbedded JMS <strong>Security</strong>, we need to enable Global <strong>Security</strong> of the applicationserver. When the security is enabled, all the JMS connections to the JMSprovider are all authenticated and access to JMS resources owned by JMSprovider are controlled by access authentications. Also, all JMS connections toJMS provider must provide a user name and password for authentication.We define this user name and password when we create a connection factory. Inthe administrative console, perform the following steps.1. Click Resources -> <strong>WebSphere</strong> JMS Provider.2. In Additional Properties, click <strong>WebSphere</strong> Queue Connection Factories.3. Click New. In this page of the Administrative Console, set the following fields:– Component-managed Authentication Alias: select an authentication aliasentry for this field. If no alias is available, you need to create one.Chapter 7. Securing Enterprise Integration components 165

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!