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

(7.3.z) Principal injected in a secured bean is different when Elytron is activated

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Major
    • None
    • None
    • Security
    • None
    • Hide

      Run the test: mvn test -Dtest=InjectPrincipalTestCase

      Repo: git@github.com:nziakova/wildfly.git
      Branch: wfly11587-followup

      When running the test without elytron there is an error on line 58 inside InjectPrincipalTestCase. This is correct behaviour and this error is expected. However this line passes when Elytron is enabled (mvn test -Dtest=InjectPrincipalTestCase -Delytron). Instead, error is thrown on line 59 but that concerns WFLY-12537 and not this issue.

      Show
      Run the test: mvn test -Dtest=InjectPrincipalTestCase Repo: git@github.com:nziakova/wildfly.git Branch: wfly11587-followup When running the test without elytron there is an error on line 58 inside InjectPrincipalTestCase. This is correct behaviour and this error is expected. However this line passes when Elytron is enabled (mvn test -Dtest=InjectPrincipalTestCase -Delytron). Instead, error is thrown on line 59 but that concerns WFLY-12537 and not this issue.

    Description

      This is a follow up on WFLY-11604. Principal should be anonymous when injected inside a bean that has RunAsPrincipal annotation but no incoming RunAs identity. This is because the call does not pass to another EJB and therefore there is no outbound call. This works for legacy but not for Elytron.

      Attachments

        Issue Links

          Activity

            People

              rhn-cservice-bbaranow Bartosz Baranowski
              rhn-engineering-lgao Lin Gao
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: