We have a secure weblogic JMS queue and are using the Direct JNDI lookup in the connector. An authentication profile is created with the credentials for the queue and providing it in the connect JMS rule the authentication for the queue fails, while using the same user name and password in the JNDI Server form (security principal and security credentials) the connect rule runs successfully.
Is it the correct behavior? How can it be altered to take the Authentication Profile in Connect JMS rule as a precedence?
Hi To Connect to the queue you should give credentials in the JNDI server rule form in security principal and security credentials and this is the correct approach to connect to and standard JMS queue from pega.
we shouldn't pass the queue credentials in the Connect-JMS rule form.