...
Keytab files are created with ktpass. Preferably on server 2008 or later. The user running ktpass must be a member of domain admin or enterprise admin.
See this section for detailed instructions.
How do I merge keytabs?
Ketyabs are merged inside Kantega Single Sign-on by uploading single keytab files and selecting to merge instead of overwriting the previous. See more on this here.
...
https://confluence.atlassian.com/conf73/configuring-secure-administrator-sessions-991928809.html
Why do I see an error message in the Jira log when a user uses “Re-authenticate with SSO?
Jira gives an error Thread corrupted! ActionContext still references a HttpSession when the websudo is established. This does not have any functional impact. The message comes due to some internal weakness and is not possible to avoid. To remove the error message from the logs, you may add this line:<logger name="com.atlassian.jira.web.filters.steps.requestcleanup.WebworkActionCleanupStep" level="OFF"/>
just above the elements </Loggers></Configuration> in the bottom of the file:${JIRA_INSTALL}/atlassian-jira/WEB-INF/classes/log4j2.xml
Kerberos will not work when using host-resolver-rule flag in Chrome to configure DNS for your server
...
Here are some docs and discussion relevant to the topic of transforming username
https://developer.atlassian.com/server/jira/platform/database-user-and-group-tables/
https://confluence.atlassian.com/jirakb/bulk-update-user-usernameinformation-andin-emailjira-using-rest-api-or-the-database-1085440914.html
https://developer.atlassian.com/server/jira/platform/database-user-and-group-tables/
https://confluence.atlassian.com/jirakb/bulk-update-user-information-in-jira-server-644875261.html server-644875261.html
My Kerberos authentication has stopped working
Potential error messages:
Parsing of the client's SPNEGO token failed with: java.lang.IllegalArgumentException: Expected tag byte should be 60, was 4e
We changed our Kerberos implemention in version 6.26.0. If you are encountering errors with Kerberos authentication after upgrading to this version please contact us through our help desk or with mail to servicedesk@kantega-sso.com. We recommend enabling the legacy Kerberos implementation as described on this page to see if it helps the issue or changes the error message: https://kantega-sso.atlassian.net/wiki/spaces/KSE/pages/1442742278/Dark+Features#Use-legacy-Kerberos
SAML and OIDC
What is the difference between SAML and OpenID Connect?
...