Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-2392

Remoting EJB identity propagation does not work with Elytron

    XMLWordPrintable

Details

    • Hide

      Checkout wildfly ladybird and run test:

      cd testsuite/elytron
      mvn clean test -Dtest=org.wildfly.test.integration.elytron.ejb.AuthenticationTestCase
      

      (need to unignore tests tagged as WFLY-7778)

      Show
      Checkout wildfly ladybird and run test: cd testsuite/elytron mvn clean test -Dtest=org.wildfly.test.integration.elytron.ejb.AuthenticationTestCase (need to unignore tests tagged as WFLY-7778 )

    Description

      Even througth succesful obtaining LoginContext, identity is not propagated in EJB call.
      Identity is unauthorized on server side.

      Remoting does not work because it is not implemented yet - this issue created primary for tests ignore issue reference.

      Often error message:

      SaslException: Authentication failed: all available authentication mechanisms failed:
         JBOSS-LOCAL-USER: Server rejected authentication
         DIGEST-MD5: Server rejected authentication]
      	at org.wildfly.naming.client.remote.RemoteNamingProvider.getPeerIdentityForNaming(RemoteNamingProvider.java:110)
      

      Attachments

        Issue Links

          Activity

            People

              jkalina@redhat.com Jan Kalina (Inactive)
              jkalina@redhat.com Jan Kalina (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: