Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kerberos Auth login frequently fails over UDP #5929

Closed
andrew-m-leonard opened this issue Jan 30, 2025 · 0 comments · Fixed by #5930
Closed

Kerberos Auth login frequently fails over UDP #5929

andrew-m-leonard opened this issue Jan 30, 2025 · 0 comments · Fixed by #5930
Assignees

Comments

@andrew-m-leonard
Copy link
Contributor

When using the default Kerberos UDP comms for login it frequently fails:

Using builtin default etypes for default_tkt_enctypes
default etypes for default_tkt_enctypes: 18 17 20 19.
>>> KrbAsReq creating message
>>> KrbKdcReq send: kdc=jckservices.adoptium.net UDP:88, timeout=30000, number of retries =3, #bytes=171
>>> KDCCommunication: kdc=jckservices.adoptium.net UDP:88, timeout=30000,Attempt =1, #bytes=171
SocketTimeOutException with attempt: 1
>>> KDCCommunication: kdc=jckservices.adoptium.net UDP:88, timeout=30000,Attempt =2, #bytes=171
SocketTimeOutException with attempt: 2
>>> KDCCommunication: kdc=jckservices.adoptium.net UDP:88, timeout=30000,Attempt =3, #bytes=171
using this Java property = java.security.auth.login.config
testURL = file:/home/jenkins/jck_root/JCK11-unzipped/JCK-runtime-11a/
The machine jckservices.adoptium.net does exist.
>>> JVM will use Java Login Config file: /home/jenkins/jck_root/JCK11-unzipped/JCK-runtime-11a/lib/jck.auth.login.config
Security Manager is null
Previous Property java.security.auth.login.config is null
Current Property java.security.auth.login.config is /home/jenkins/jck_root/JCK11-unzipped/JCK-runtime-11a/lib/jck.auth.login.config
Port #60834 was allocated as a free port.  This test will use this port.
Security Manager is null
<GSSCallbackHandler> callbacks.length = 1
<GSSCallbackHandler> Inside GSSCallbackHandler, callbacks is NameCallback.
Kerberos username [aleonardf4y]:  user2/jckservices.adoptium.net@ADOPTIUM_NET
<GSSCallbackHandler> callbacks.length = 1
<GSSCallbackHandler> Inside GSSCallbackHandler, callbacks is PasswordCallback.
Kerberos XXXX for user2/jckservices.adoptium.net@ADOPTIUM_NET: XX
Status return from the server thread: Failed. Authentication took too long, time expired.

Symptoms indicate likely intermittent problems with Firewall configurations.
Changing to use TCP rather than UDP, always succeeds.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant