Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

How should I take care of issues like security while implementing a QueueConnectionFactory and other administered objects in JMS?

April 26, 2017administered implementing JMS objects security

0

Posted

How should I take care of issues like security while implementing a QueueConnectionFactory and other administered objects in JMS?

1 Answer

0

Posted

Location: http://www.jguru.com/faq/view.jsp?EID=134239 Created: Aug 24, 2000 Modified: 2000-08-24 15:06:54.755 Author: Jerry Smith (http://www.jguru.com/guru/viewbio.jsp?EID=9) Question originally posed by saima rizvi (http://www.jguru.com/guru/viewbio.jsp?EID=64672 JMS does not define a security API. JMS implementations provide vendor-specific security facilities, typically, through a text-oriented console or a graphical browser/console. For this reason, (distributed) JMS clients should use a topic and queue design within their application components that facilitates the factoring of and provision of security at several levels–whatever matches the needs of the application components. In this way, an administrator can set the security characteristics of various topics and queues to allow the proper level of accessibility by user and by application functionality.