Skip to content
New issue

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

SSO Attlassian -> Gitlab (new user) #1096

Closed
webcodecs opened this issue Oct 17, 2022 · 1 comment
Closed

SSO Attlassian -> Gitlab (new user) #1096

webcodecs opened this issue Oct 17, 2022 · 1 comment

Comments

@webcodecs
Copy link

Please complete all sections.

Configuration

  • Provider Gem: omniauth-atlassian_oauth2*
  • Ruby Version: ``
  • Framework: gitlab 15.2
  • Platform: 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:

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.

Steps to Reproduce

  • create gitlab instance
  • install omniauth_attlassian_oauth2 driver
  • create atlassian app to authenticate
  • try to register as a new user in gitlab instance via SSO

Im not 100 percent sure if its correct to publish the issue here. But i wanted to give a try

Thanks in advandce

@BobbyMcWho
Copy link
Member

This sounds like an issue with Gitlab or whatever atlassian OmniAuth strategy it uses, not an OmniAuth bug

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants