Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-19838

No HttpServerAuthenticationMechanismFactory available if there is one war using OIDC

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • None
    • 33.0.0.Final
    • Security
      • create war with web.xml auth-type=BASIC
      • create war with web.xml auth-type=OIDC
      • wrap both wars together to one ear
    • Migration
    • ---
    • ---

      When deploying a WAR file with a web.xml (auth-type=BASIC) it works as expected, there ist a HttpServerAuthenticationMechanismFactory provided by factories in AggregateServerMechanismFactory: [..BASIC..FORM..etc] thats getting active when accessing a secured resource.

      When wraping that WAR inside an EAR File there is no Problem, it works equal as above.

      But when deploying a second WAR with web.xml (auth-type=OIDC) inside the same EAR, the Auth Mechanism BASIC,FORM etc is not available for the first WAR!

      The Log "HttpServerAuthenticationMechanismFactory provided by factories ..." is completly gone.

      If both WARs use BASIC it works, and the Log message is displayed two times.

      Feels like a bug, shouldnt be possible to use BASIC in on WAR and OIDC in another WAR ?

       

            fjuma1@redhat.com Farah Juma
            hinderkott Matthias Hinderkott
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: