On Fri, 24 Apr 2026 15:29:12 GMT, Kieran Farrell <[email protected]> wrote:
>> In DNS-based KDC discovery failures are exposed as generic 'KrbException: >> Cannot locate KDC / Unable to locate KDC for realm <REALM>' with no >> indication whether the underlying DNS SRV lookup failed due to NXDOMAIN, >> SERVFAIL, or a communication timeout. >> >> To improve supportability, this patch updates >> `KrbServiceLocator.getKerberosService(realm, protocol)` to rethrow the >> original JNDI NamingException from the SRV lookup and attach a sanitized >> failure category to the existing KrbException when both udp and tcp >> discovery attempts fail, while preserving the original top level exception >> message. `Config.getKDCFromDNS()` is updated to catch exception, sanitize it >> into the relevant category to prevent leaking any senistive information and >> attach it to the existing KrbException. >> >> >> --------- >> - [x] I confirm that I make this contribution in accordance with the >> [OpenJDK Interim AI Policy](https://openjdk.org/legal/ai). > > Kieran Farrell has updated the pull request incrementally with one additional > commit since the last revision: > > update Marked as reviewed by weijun (Reviewer). Please add a `noreg-*` label to the JBS issue. ------------- PR Review: https://git.openjdk.org/jdk/pull/30824#pullrequestreview-4171644075 PR Comment: https://git.openjdk.org/jdk/pull/30824#issuecomment-4314337865
