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

SPNEGO, when user not in realm 401 is returned

    XMLWordPrintable

Details

    • Bug
    • Resolution: Not a Bug
    • Major
    • None
    • 7.1.0.GA
    • Security
    • None
    • Hide 
      ./build-eap71.sh -Deap -Dversion.jboss.bom=7.1.0.GA -Dversion.wildfly.core=3.0.10.Final-redhat-1 -Dmaven.repo.local=/home/mchoma/workspace/eap-versions/7.1.0.CR4/jboss-eap-7.1.0.GA-maven-repository/maven-repository -Djboss.dist.zip=/home/mchoma/workspace/eap-versions/7.1.0.CR4/jboss-eap-7.1.0.CR4.zip -Dtest=SPNEGOSessionTestCase -DtestLogToFile=false -Dignore.known.issues=true
      Show
      ./build-eap71.sh -Deap -Dversion.jboss.bom=7.1.0.GA -Dversion.wildfly.core=3.0.10.Final-redhat-1 -Dmaven.repo.local=/home/mchoma/workspace/eap-versions/7.1.0.CR4/jboss-eap-7.1.0.GA-maven-repository/maven-repository -Djboss.dist.zip=/home/mchoma/workspace/eap-versions/7.1.0.CR4/jboss-eap-7.1.0.CR4.zip -Dtest=SPNEGOSessionTestCase -DtestLogToFile= false -Dignore.known.issues= true

    Description

      When I successfully authenticate using SPNEGO, but user is not stored in underlying security realm, 401 is returned. Whereas I would expect 403. Because authentication was successful, but authorization part failed.

      Also In SPNEGO + FORM fallback scenario, when invalid ticket is used, http form with http status code 401 is send, where I would expect 200.

      This JIRA is just for reference purpose and just catch up on consequence of existing PR https://github.com/wildfly-security/wildfly-elytron/pull/1022

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-12868 [QE](7.1.z) ELY-1373 - IBM JDK, SPNEGO + FORM; with invalid ticket 200 status code is returned

          • 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.
          • Closed

          Activity

            People

              jkalina@redhat.com Jan Kalina (Inactive)
              mchoma@redhat.com Martin Choma
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: