You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 12, 2019. It is now read-only.
Seeing an issue on a production jabberd instance where the server is tied to kerberos being available for the server. This server config has kerberos authentication specifically not configured, instead using a custom table on a postgresql server as the auth path. What has been observed several times now is that when the kerberos server (IPA) is not available to the jabberd server authentications hang. Doing strace of the c2s process shows kerberos calls before the call to the database for authentication.
Happy to provide any additional information or debugging logs.
The text was updated successfully, but these errors were encountered:
I saw something earlier, and my slightly fuzzy memory is that I tracked it down to gsasl trying to contact the KDC when I don't see why it should. I do not remember finding a resolution.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Seeing an issue on a production jabberd instance where the server is tied to kerberos being available for the server. This server config has kerberos authentication specifically not configured, instead using a custom table on a postgresql server as the auth path. What has been observed several times now is that when the kerberos server (IPA) is not available to the jabberd server authentications hang. Doing strace of the c2s process shows kerberos calls before the call to the database for authentication.
Happy to provide any additional information or debugging logs.
The text was updated successfully, but these errors were encountered: