...
Our testing shows that during such a setup getting a Kerberos ticket form AD will not work. So when testing Kerberos you will either have to configure this link between jira.example.com and IP in your DNS servers or in your local hosts file.
I am unable to log in with traditional login when I press “Log in again”. I am instead automatically logged in, and redirected to dashboard.
This situation occurs when Kerberos is configured and force login is enabled. To allow users to log in with traditional login, visit Kantega SSO → Common → Force Login. At the bottom of the page there is a section called “After login behavior”. Toggling this slider off should allow users to log in with username and password after pressing “Log in again”.
User Directories
How are Kerberos users mapped to accounts in User Directories?
Kerberos uses the sAMAccountName Active Directory attribute to identify users.
Kantega SSO will extract this username from the client's Kerberos Principal Name and use that when looking up users in User Directories.
Example: If the Kerberos Principal Name is "johndoe@EXAMPLE.LOCAL", Kantega SSO will search User Directories for the account "johndoe".
...
User Directories
How are Kerberos users mapped to accounts in User Directories?
Kerberos uses the sAMAccountName Active Directory attribute to identify users.
Kantega SSO will extract this username from the client's Kerberos Principal Name and use that when looking up users in User Directories.
Example: If the Kerberos Principal Name is "johndoe@EXAMPLE.LOCAL", Kantega SSO will search User Directories for the account "johndoe".
This means that if your accounts are named with the standard username attribute, you can use any of the User Directory types supported by Atlassian:
...
You will have to wait up to one minute after the file is deleted before username/password login works.
I am unable to log in with traditional login when I press “Log in again”. I am instead automatically logged in, and redirected to dashboard.
This situation occurs when Kerberos is configured and force login is enabled. To allow users to log in with traditional login, visit Kantega SSO → Common → Force Login. At the bottom of the page there is a section called “After login behavior”. Toggling this slider off should allow users to log in with username and password after pressing “Log in again”.
How can I bulk transform usernames in Jira?
...