[jboss-jira] [JBoss JIRA] (ELY-715) SPNEGO: missing negstat field in the first reply
Jan Kalina (JIRA)
issues at jboss.org
Tue Mar 20 12:31:00 EDT 2018
[ https://issues.jboss.org/browse/ELY-715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jan Kalina reopened ELY-715:
----------------------------
Assignee: Jan Kalina (was: Darran Lofthouse)
Sorry, it looks I was wrong...
>From *testInvalidKerberosSpnegoWorkflow* in tests-ldap-kerberos dubugging results GSSContext provides negState response, but we dont use it if connection is already established (=no continuation is needed).
Reopening, working on fix.
> SPNEGO: missing negstat field in the first reply
> ------------------------------------------------
>
> Key: ELY-715
> URL: https://issues.jboss.org/browse/ELY-715
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Authentication Mechanisms
> Reporter: Jan Kalina
> Assignee: Jan Kalina
> Fix For: 1.1.0.CR2
>
>
> When the client sends an initial SPNEGO token with Kerberos as preferred mechanism and includes an invalid kerberos token, then client expects to see the {{WWW-Authenticate}} HTTP header with SPNEGO response {{negTokenResp[ negState = reject ]}}.
> As stated in [SPNEGO specification|https://tools.ietf.org/html/rfc4178#section-4.2.2] negstat is required in first reply:
> {code:borderStyle=dashed}
> negState
> ...
> This field is REQUIRED in the first reply from the target, and is
> OPTIONAL thereafter. When negState is absent, the actual state
> should be inferred from the state of the negotiated mechanism
> context.
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
More information about the jboss-jira
mailing list