Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-17721

[GSS](7.2.z) EJB/JNDI over HTTP-Invoker Throws CommunicationException instead of AuthenticationException

    Details

      Description

      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.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  thofman Tomas Hofman
                  Reporter:
                  thofman Tomas Hofman
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  4 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: