JDK-4460767 : GSS-Krb5 mechananism should support KRB-ERROR token encapsulation
  • Type: Enhancement
  • Component: security-libs
  • Sub-Component: org.ietf.jgss:krb5
  • Affected Version: 1.4.0
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: solaris_8
  • CPU: generic
  • Submitted: 2001-05-18
  • Updated: 2005-08-17
  • Resolved: 2005-08-17
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6
6Resolved
Related Reports
Duplicate :  
JDK-6228529 - JDK on Windows does not wait for preauthorizaion record from Kerberos and causes an error
Description
The GSS-krb5 mechanism passes tokens from the Kerberos protocol encapsulated in GSS style messages. When the mechanism receives a GSS style token it looks at the tkekn type to determine which Kerberos protocol message it contains. Currently, the token type for the KRB-ERROR message is not supported and receiving it will cause an exception saying that the token was improper.

The KRB-ERROR message is mostly utilized as part of context establishment in GSSKrb5 to indicate a failure. One scenario when the server sends this to the client is when the client sends the context establishment token to the wrong server identity.
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: dragon
01-09-2004
EVALUATION sharon.liu@eng 2001-07-13 Yup, plan to fix in Tiger. [ Seema Malkani ] I have added support to parse the KRB-ERROR, and in addition, have added support for the new Pre-authentication types returned in the KRB-ERROR message, as defined in the latest Kerberos specification. This has been fixed as bug 6228529. This bug is a duplicate of bug 6228529. Hence closing this bug.
01-09-2004