EJB over Http-invoker throws CommunicationException on Authentication Failure

Solution Verified - Updated -

Issue

  • A CommunicationException is thrown but ideally it would be an an AuthenticationException like with http-remoting
  • Log shows this message:

    HTTP000005: Invalid response code 401 (full response ClientResponse{responseHeaders={www-authenticate=[Basic realm="LDAPRealm"], content-length=[77], content-type=[text/html], date=[Thu, 25 Jul 2019 00:16:43 GMT]}, responseCode=401, status='', protocol=HTTP/2.0})
    

Environment

  • Red Hat JBoss Enterprise Application Platform (JBoss EAP)
    • 7.2
  • Enterprise Java Beans (EJB)
  • Http-Invoker
  • EJBException wrapping real exception caught in client code on authentication failure

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In