When I set up my pangolin instance before OAuth was supported, I made my user "me@mydomain.com." Now I would like to set up my Azure SSO. However, the username I would use is the email I used for the owner account. Any attempts to add the user fail because it already exists.
I am hoping for the ability to make a new internal account at a backup email, promote it to owner, and then use my Azure account for SSO.
Thanks,
Originally created by @nightchrono on GitHub (May 4, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/672
When I set up my pangolin instance before OAuth was supported, I made my user "me@mydomain.com." Now I would like to set up my Azure SSO. However, the username I would use is the email I used for the owner account. Any attempts to add the user fail because it already exists.
I am hoping for the ability to make a new internal account at a backup email, promote it to owner, and then use my Azure account for SSO.
Thanks,
@oschwartz10612 commented on GitHub (May 5, 2025):
Thanks for the suggestion! I am going to move this to a discussion so it can be upvoted and prioritized for addition!
<!-- gh-comment-id:2849630378 -->
@oschwartz10612 commented on GitHub (May 5, 2025):
Thanks for the suggestion! I am going to move this to a discussion so it can be upvoted and prioritized for addition!
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @nightchrono on GitHub (May 4, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/672
When I set up my pangolin instance before OAuth was supported, I made my user "me@mydomain.com." Now I would like to set up my Azure SSO. However, the username I would use is the email I used for the owner account. Any attempts to add the user fail because it already exists.
I am hoping for the ability to make a new internal account at a backup email, promote it to owner, and then use my Azure account for SSO.
Thanks,
@oschwartz10612 commented on GitHub (May 5, 2025):
Thanks for the suggestion! I am going to move this to a discussion so it can be upvoted and prioritized for addition!