Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8227437

S4U2proxy cannot continue because server's TGT cannot be found

    XMLWordPrintable

    Details

    • Subcomponent:
    • Introduced In Build:
      b25
    • Resolved In Build:
      b31
    • Verification:
      Verified

      Backports

        Description

        With JDK-8215032, if the intermediate server name is an alias, its TGT would have a different client name. When the server is about to perform a S4U2proxy request, it needs to find its TGT first. However, since the TGT have a different name SubjectComber::find will not find it and thus S4U2proxy fails..

          Attachments

            Issue Links

            backported by

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8228518 S4U2proxy cannot continue because server's TGT cannot be found

            • P2 - Crashes, loss of data, severe memory leak.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8228789 S4U2proxy cannot continue because server's TGT cannot be found

            • P2 - Crashes, loss of data, severe memory leak.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8229063 S4U2proxy cannot continue because server's TGT cannot be found

            • P2 - Crashes, loss of data, severe memory leak.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8234521 S4U2proxy cannot continue because server's TGT cannot be found

            • P2 - Crashes, loss of data, severe memory leak.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8237161 S4U2proxy cannot continue because server's TGT cannot be found

            • P2 - Crashes, loss of data, severe memory leak.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8239192 S4U2proxy cannot continue because server's TGT cannot be found

            • P2 - Crashes, loss of data, severe memory leak.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8251749 S4U2proxy cannot continue because server's TGT cannot be found

            • P2 - Crashes, loss of data, severe memory leak.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8245799 S4U2proxy cannot continue because server's TGT cannot be found

            • P2 - Crashes, loss of data, severe memory leak.
            • Closed

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8249125 S4U2proxy cannot continue because server's TGT cannot be found

            • P2 - Crashes, loss of data, severe memory leak.
            • Closed
            relates to

            Bug - A problem which impairs or prevents the functions of the product. JDK-8227381 GSS login fails with PREAUTH_FAILED

            • P3 - Major loss of function.
            • Resolved

            Bug - A problem which impairs or prevents the functions of the product. JDK-8256659 Incorrect parsing of krb5 username

            • P3 - Major loss of function.
            • Closed

            Enhancement - null JDK-8215032 Support Kerberos cross-realm referrals (RFC 6806)

            • P4 - Minor loss of function, or other problem where easy workaround is present.
            • Resolved

              Activity

                People

                Assignee:
                mbalao Martin Balao
                Reporter:
                weijun Weijun Wang
                Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved: