Show TOC

 JMS Provider Security AspectsLocate this document in the navigation structure

The JMS connection factories are obtained using JNDI. A JMS connection can be created from the connection factory either with a user name and password, or with no parameters.

  • In case a user name and password are provided, a validation check will be performed if the password matches the user. If not, the call will fail. If the check is successful, all subsequent JMS permission checks will be done for the specified user.
  • In case a connection is created without specifying the user name and password, all subsequent JMS permission checks will be done for the user in the current thread context (this will be the anonymous user, if no login has been performed).

Note that in both cases no logon is performed, only JMS permission checks are done for the respective user.

Communication Protocol

The JMS Provider communication uses a SAP-proprietary binary protocol on top of P4 as the transport layer. The JMS provider does not offer its own encryption on the JMS communication, but the P4 transport can be configured to run over SSL.

Data Storage

Configuration data and user data (messages) are stored in the database and underlie the database protection mechanisms.