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

Legacy Kerberos for management interface returns 500 instead of 401

    XMLWordPrintable

Details

    • Regression
    • Hide

      Tested scenario https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/how-to-set-up-sso-with-kerberos/#configure-krb-management-interfaces

      With difference that Kerberos is configured wrongly, e.g. in way there is provided wrong principal or wrong for host attribute. 

                  <security-realm name="NotSuitableKeyTab">
                <server-identities>
                    <kerberos>
                        <keytab principal="HTTP/wronghost@JBOSS.ORG" path="krb-http.keytab" for-hosts="wronghost"/>
                        <keytab principal="HTTP/wronghost2@JBOSS.ORG" path="krb-http.keytab" for-hosts="wronghost2"/>
                    </kerberos>
                </server-identities>
                <authentication>
                    <kerberos/>
                </authentication>
            </security-realm>

      2. On first access to http://localhost:9990/console server responses with http code 500 instead of expected 401.

      Show
      Tested scenario https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/how-to-set-up-sso-with-kerberos/#configure-krb-management-interfaces With difference that Kerberos is configured wrongly, e.g. in way there is provided wrong principal or wrong for host attribute. <security-realm name= "NotSuitableKeyTab" > <server-identities> <kerberos> <keytab principal= "HTTP/wronghost@JBOSS.ORG" path= "krb-http.keytab" for -hosts= "wronghost" /> <keytab principal= "HTTP/wronghost2@JBOSS.ORG" path= "krb-http.keytab" for -hosts= "wronghost2" /> </kerberos> </server-identities> <authentication> <kerberos/> </authentication> </security-realm> 2. On first access to http://localhost:9990/console server responses with http code 500 instead of expected 401.

    Description

      On first access server should response with 401 http code. Subsequent response could be 500, as it express properly server is misconfigured. In EAP 7.0 it was 403, that is not ideal as 403 mean user is authenticated but has not proper roles, which is not true in this case.

      Also some ERROR log message would be helpful for administrators to find cause of problem. Now there are just TRACE level messages

      server.log
      07:40:04,134 TRACE [org.jboss.as.domain.management.security] (management task-6) No mapping for name 'http/localhost.localdomain' to KeytabService, attempting to use host only match.
07:40:04,135 TRACE [org.jboss.as.domain.management.security] (management task-6) No mapping for host 'localhost.localdomain' to KeytabService, attempting to use default.
07:40:04,135 TRACE [org.jboss.as.domain.management.security] (management task-6) No KeytabService available for host 'localhost.localdomain' unable to return SubjectIdentity.

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-2438 Legacy Kerberos for management interface returns 500 instead of 401

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-9571 (7.1.0) Upgrade to WildFly Core to 3.0.0.Beta13

          • 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.
          • Verified
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-9945 Elytron, be consistent with legacy for misconfigured kerberos authentication of http management interface

          • 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

          Activity

            People

              darran.lofthouse@redhat.com Darran Lofthouse
              mchoma@redhat.com Martin Choma
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: