[com.w.p.j.u.UmJMSClient] - Unable to create JNDI context: peer not authenticated

, ,
1

  1. Below error is thrown continuously in the sag-osgi.log.
    [com.w.p.j.u.UmJMSClient] - Unable to create JNDI context: peer not authenticated
    Anyone knows what causes this error and how to fix this?

  2. Whenever we create a system user in MWS, the user is not able to authenticate while launching an IS service with the Execute ACL same as the one the new user is part of, unless the IS is restarted. Is there any way to make this work without restart in 10.15?

Are both the above issues connected in anyway?

2
  • You should check that JMS client and server are both configured to use compatible SSL/TLS protocols.
  • Double-check the JNDI properties used to create the initial context. These should include the correct URL, factory class, and any SSL-related properties such as keystore and truststore locations and passwords.
  • Also, I recommend to check that there are no network issues preventing the client from reaching the server (i.e. Firewalls, proxies)