[jboss-jira] [JBoss JIRA] (WFLY-12444) EJB/JNDI over HTTP-Invoker Throws CommunicationException instead of AuthenticationException

[Tomas Hofman (Jira)]

     [ https://issues.jboss.org/browse/WFLY-12444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tomas Hofman updated WFLY-12444:
--------------------------------
    Affects Version/s: 17.0.1.Final


> EJB/JNDI over HTTP-Invoker Throws CommunicationException instead of AuthenticationException
> -------------------------------------------------------------------------------------------
>
>                 Key: WFLY-12444
>                 URL: https://issues.jboss.org/browse/WFLY-12444
>             Project: WildFly
>          Issue Type: Bug
>          Components: EJB
>    Affects Versions: 17.0.1.Final
>         Environment: * Red Hat JBoss Enterprise Application Server (JBoss EAP) 7.2
> * EJB / JNDI
> * undertow http-invoker
> * Authentication Failure
>            Reporter: Tomas Hofman
>            Assignee: Tomas Hofman
>            Priority: Major
>
> Switching from http-remoting to the http-invoker when calling an EJB, if an authentication failure occurs, the exception wrapped in the EJBException has changed.
> It was a javax.naming.AuthenticationException before, but now it's throwing a CommunicationException even though the log shows it's getting a 401 from the server:
> WFHTTP000005: Invalid response code 401 (full response ClientResponse{responseHeaders={www-authenticate=[Basic realm="MyRealm"], content-length=[77], content-type=[text/html], date=[Thu, 28 Jul 2019 12:18:43 GMT]}, responseCode=401, status='', protocol=HTTP/2.0})
> Before, AuthenticationException could be used for logic flow, but communication exception is too general.



--
This message was sent by Atlassian Jira
(v7.13.5#713005)