8000 SSO Provider not working with new alias / secondary domain (Google Workspaces) · Issue #5188 · outline/outline · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

SSO Provider not working with new alias / secondary domain (Google Workspaces) #5188

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.

Sign up for GitHub

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

Jump to bottom
Closed
Jamira40 opened this issue Apr 11, 2023 · 4 comments
Closed

SSO Provider not working with new alias / secondary domain (Google Workspaces) #5188

Jamira40 opened this issue Apr 11, 2023 · 4 comments
Labels
bug self-hosted Issues related to self-hosting the code

Comments

@Jamira40
Copy link
Jamira40 commented Apr 11, 2023 •
edited
Loading

A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

  1. Added secondary Alias for few accounts. For example originaldomain.com and we added newdomain.com to our Google Workspace.
  2. Whitelisted domain at Outline Administration. Currently have two domains.
  3. Tried to login to Outline with Google Account that was previously registered with user@originaldomain.com but now its user@newdomain.com but same Workspace Account (ID is same)

Error Logs
{"error":"User authentication 1051**********484 already exists for 931**********-54**-46**-86f3-5**********103, tried to assign to c88**********-ac**-4d**-8096-c**********a70","stack":"UnauthorizedError: User authentication 1051**********484 already exists for 931**********-54**-46**-86f3-5**********103, tried to assign to c88**********-ac**-4d**-8096-c**********a70\n at AuthenticationError (/opt/outline/build/server/errors.js:38:34)\n at accountProvisioner (/opt/outline/build/server/commands/accountProvisioner.js:118:43)\n at runMicrotasks (<anonymous>)\n at processTicksAndRejections (node:internal/process/task_queues:96:5)","level":"error","message":"Error during authentication"}

Expected behavior
Able to access same account and assign new email.

Screenshots
If applicable, add screenshots or videos to help explain your problem.

Outline (please complete the following information):

  • Install: Self Hosted
  • Version: Docker 0.68.0

Desktop (please complete the following information):

  • OS: macOS
  • Browser Chrome
  • Version 110.0.5481.100
@Jamira40 Jamira40 added the bug label Apr 11, 2023
@Jamira40
Copy link
Author

Looks similar to #4668

@tommoor
Copy link
Member
tommoor 8000 commented Apr 11, 2023

Currently to overcome this you would need to manually add a new row to the authentication_providers table in the database with the new domain. There isn't any functionality in the UI built yet for this case.

@tommoor tommoor added the self-hosted Issues related to self-hosting the code label Apr 11, 2023
@tommoor
Copy link
Member
tommoor commented Apr 11, 2023

Merging into #1945

@tommoor tommoor closed this as completed Apr 11, 2023
@Jamira40
Copy link
Author

Checked authentication_providers and I can see two providers already. So adding it manually is not necessary / possible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug self-hosted Issues related to self-hosting the code
Projects
None yet
Milestone
No milestone
31DC
Development

No branches or pull requests
2 participants
@tommoor @Jamira40
0