...
You will have to wait up to one minute after the file is deleted before username/password login works.
How can I bulk transform usernames in Jira?
Here are some docs and discussion relevant to the topic of transforming username
...
We are unable to log in with traditional login on Jira. When we press “Log in again”, we are instead automatically logged in with Kerberos and redirected to Jira’s 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?
Here are some docs and discussion relevant to the topic of transforming username
...
More info about SAML and OpenID Connect
OIDC
Why do I get an error message with HTTP 401 UNAUTHORIZED: Please check that your client_secret is correct?
The following error message indicates that the IDP no longer accepts the configured client secret: [OIDC-K6JCV4L81E] Failed performing OIDC POST request: Expected HTTP 200 OK. Actual response was HTTP 401 UNAUTHORIZED Please check that your client_secret is correct.
Possible explanations:
The client secret for you OIDC integration is expired.
You accidentally copy/pasted in the wrong value. E.g. Microsoft Entra ID /Azure AD offers a secret ID field which is often confused with the client secret itself
Environment
Which Identity Providers do you support?
...