We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Please complete all sections.
omniauth-atlassian_oauth2*
gitlab 15.2
Atlassian
If i use the SSO with my Attlassian account to register for my gitlab instance i expect to have a new user and dont got an error.
If i try to register via attlassian account, i got an 500 error. My sentry says the following:
ActiveRecord::StatementInvalid PG::CheckViolation: ERROR: new row for relation "atlassian_identities" violates check constraint "atlassian_identities_refresh_token_length_constraint"
if an already registered user signs in via SSO, its working. Like the error message says, it happens only on inserting a new user row.
Im not 100 percent sure if its correct to publish the issue here. But i wanted to give a try
Thanks in advandce
The text was updated successfully, but these errors were encountered:
This sounds like an issue with Gitlab or whatever atlassian OmniAuth strategy it uses, not an OmniAuth bug
Sorry, something went wrong.
No branches or pull requests
Please complete all sections.
Configuration
omniauth-atlassian_oauth2*
gitlab 15.2
Atlassian
Expected Behavior
If i use the SSO with my Attlassian account to register for my gitlab instance i expect to have a new user and dont got an error.
Actual Behavior
If i try to register via attlassian account, i got an 500 error. My sentry says the following:
if an already registered user signs in via SSO, its working. Like the error message says, it happens only on inserting a new user row.
Steps to Reproduce
Im not 100 percent sure if its correct to publish the issue here. But i wanted to give a try
Thanks in advandce
The text was updated successfully, but these errors were encountered: