Enabling secure JMS messaging for the Liberty profile

Use the wasJmsSecurity-1.0 Liberty feature to make the wasJmsServer-1.0 feature work in a secure mode. Securing the messaging resources ensures that only authenticated and authorized users can access the messaging resources such as queues, topics, and messages.

Subtopics

• Authenticating users to connect to the messaging engine
  You must validate the users credentials so that the user is authenticated to connect to the messaging engine.
• Authorizing users to connect to the messaging engine
  You must validate if the authenticated users have sufficient permissions to access the messaging resources (that is queues or topic) to perform actions like sending, receiving, or browsing messages.

Parent topic: Enabling JMS messaging for the Liberty profile

Related concepts:

Liberty embedded JMS messaging provider

Service integration bus messaging provider

Related tasks:

Enabling JMS messaging for a single Liberty profile server

Enabling JMS messaging between two Liberty profile servers

Enabling interoperability between the Liberty profile and WebSphere Application Server full profile

Securing JMS communications in the Liberty profile by using SSL

Getting started with security in the Liberty profile

Setting up BasicRegistry and role mapping on the Liberty profile

Configuring a basic user registry for the Liberty profile

Configuring LDAP user registries with the Liberty profile

Task topic

---

Terms and conditions for information centers | Feedback


Last updated: Wednesday, 22 May 2013
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-mp&topic=twlp_msg_sec
File name: twlp_msg_sec.html