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

Elytron DIGEST misconfiguration not handled

    XMLWordPrintable

Details

      1. ./standalone.sh -c standalone-elytron.xml
      2. deploy secured-webapp.war
      3. access localhost:8080/secured-webapp/index.jsp
      4. User can't get in and keep getting 401 http status code

    Description

      When realm name from web.xml and server configuration differs, user is not informed about that fact.

      Could misconfiguration be handled by failing during application deployment as application requirement could not be satisfied?

      web.xml
        <login-config>
      <auth-method>DIGEST</auth-method>
      <realm-name>Secured kingdom</realm-name>
  </login-config>
      standalone-elytron.xml
      <http-authentication-factory name="application-http-authentication" http-server-mechanism-factory="global" security-domain="ApplicationDomain">
    <mechanism-configuration>
        <mechanism mechanism-name="DIGEST">
            <mechanism-realm realm-name="ApplicationRealm"/>
        </mechanism>
    </mechanism-configuration>
</http-authentication-factory>
      server.log
      17:06:18,278 TRACE [org.wildfly.security] (default task-1) Handling MechanismInformationCallback
17:06:18,282 TRACE [org.wildfly.security] (default task-1) New nonce generated AAAAAQAAGoxim7G7FMLLnVddA7s69JDh5sRsiZ5aEDhg7qf+dB2Rjs7xwrg=, using seed Secured kingdom
17:06:22,308 TRACE [org.wildfly.security] (default task-2) Handling MechanismInformationCallback
17:06:22,311 TRACE [org.wildfly.security] (default task-2) Handling AvailableRealmsCallback: realms = [Application Realm]
17:06:22,312 TRACE [org.wildfly.security] (default task-2) Handling AvailableRealmsCallback: realms = [Application Realm]
17:06:22,312 TRACE [org.wildfly.security] (default task-2) Handling RealmCallback: selected = [Secured kingdom]
17:06:22,314 TRACE [org.wildfly.security] (default task-2) New nonce generated AAAAAgAAGo1TCzTJDpmA8HsI2fS4ZfJ60KbECZU6edCP9UepmGnyV93iP6c=, using seed Secured kingdom

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-7569 Elytron DIGEST misconfiguration not handled

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified
          relates to

          Task - Represents a small unit of work that is not end-user facing. ELY-1114 Check for realm availability when selecting a DIGEST mechanism realm

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

              Unassigned Unassigned
              mchoma@redhat.com Martin Choma
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: