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

Remoting EJB identity propagation does not work with Elytron

    XMLWordPrintable

Details

    • Blocks Testing
    • Hide

      Tests in testsuite/elytron: (need to unignore tests tagged as WFLY-7778)
      org.wildfly.test.integration.elytron.ejb.AuthenticationTestCase.testAuthentication()
      org.wildfly.test.integration.elytron.ejb.AuthenticationTestCase.testAuthentication_BadPwd()
      org.wildfly.test.integration.elytron.ejb.AuthenticationTestCase.testAuthentication_TwoBeans()
      org.wildfly.test.integration.elytron.ejb.AuthenticationTestCase.testAuthentication_TwoBeans_ReAuth_BadPwd()

      Show
      Tests in testsuite/elytron : (need to unignore tests tagged as WFLY-7778 ) org.wildfly.test.integration.elytron.ejb.AuthenticationTestCase.testAuthentication() org.wildfly.test.integration.elytron.ejb.AuthenticationTestCase.testAuthentication_BadPwd() org.wildfly.test.integration.elytron.ejb.AuthenticationTestCase.testAuthentication_TwoBeans() org.wildfly.test.integration.elytron.ejb.AuthenticationTestCase.testAuthentication_TwoBeans_ReAuth_BadPwd()

    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

          blocks

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-10788 Fix and unignore tests for switching identities in Elytron

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Resolved
          clones

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-2392 Remoting EJB identity propagation does not work with Elytron

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          links to

          Web Link KCS

          Activity

            People

              dlloyd@redhat.com David Lloyd
              josef.cacek@gmail.com Josef Cacek (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: