-
Bug
-
Resolution: Fixed
-
P4
-
8
-
b61
-
generic
-
generic
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8005656 | 7-pool | Mala Bankal | P4 | Closed | Other | |
JDK-8005657 | 7u45 | Mala Bankal | P2 | Closed | Fixed | b01 |
JDK-8000744 | 7u40 | Weijun Wang | P4 | Closed | Fixed | b01 |
useTicketCache normally used in the intiator side, and storeKey on the acceptor side. When both are set to true, and a valid TGT is found inside the cache, no password or keytab will be required, and therefore no key to store.
This combination is useless and should have been set to illegal. However, some customers simply set a lot of arguments to true and this will actually work if password or key is used. We don't want to break their programs.
For this case, when there is no key but storeKey is true, a proper LoginException should be thrown. This is also consistent with the JDK 6 behavior.
This combination is useless and should have been set to illegal. However, some customers simply set a lot of arguments to true and this will actually work if password or key is used. We don't want to break their programs.
For this case, when there is no key but storeKey is true, a proper LoginException should be thrown. This is also consistent with the JDK 6 behavior.
- backported by
-
JDK-8005657 Krb5LoginModule shows NPE when both useTicketCache and storeKey are set to true
-
- Closed
-
-
JDK-8000744 Krb5LoginModule shows NPE when both useTicketCache and storeKey are set to true
-
- Closed
-
-
JDK-8005656 Krb5LoginModule shows NPE when both useTicketCache and storeKey are set to true
-
- Closed
-