Skip to content

Allow transferring workspaces to another user or change email of Okta-based users #10280

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
yoshi23 opened this issue Oct 16, 2023 · 4 comments
Closed

Allow transferring workspaces to another user or change email of Okta-based users #10280

yoshi23 opened this issue Oct 16, 2023 · 4 comments
Labels
waiting-for-info The issue creator is asked to provide more information.

Comments

@yoshi23
Copy link

yoshi23 commented Oct 16, 2023

Hi, my company had a change of domain name and users have a new email in Okta. Adding the new domain to the Okta integration will let people log in but Coder sees them as new users with their new email and their workspaces are not accessible. Is there a way to do a one-off fix for somehow make Coder aware that the new emails belong to the same people, or to update the workspaces to be owned by the new user? Thanks a lot!
@cdr-bot cdr-bot bot added the feature label Oct 16, 2023
@elliot-graebert-skydio
Copy link

I'd like to add a +1, but simply for the ability to transfer workstations between users. I'm fine it this requires some type of restart as part of transfer or something. The use case I ran into this week was a dev that built a cool experiment, and wanted to give it to a coworker to try from there.

@github-actions github-actions bot added the stale This issue is like stale bread. label Apr 15, 2024
@MrPeacockNLB
Copy link
Contributor

From security perspective this is a no-go. Workspace are user bonded and contains secrets. Save your work and start a new fresh workspace.

@matifali
Copy link
Member

The email address should update automatically for all OIDC accounts when there is a change in the upstream identity provider. If not, then it's a bug that needs to be fixed. There was a corner case which was fixed in #10972.

There is an open issue with syncing usernames for OIDC provisioned accounts additionally.

@matifali matifali added waiting-for-info The issue creator is asked to provide more information. and removed stale This issue is like stale bread. feature labels Apr 15, 2024
@yoshi23
Copy link
Author

yoshi23 commented Apr 15, 2024

Thank you for the feedback. This was a one time challenge in the past for us, I'm happy to close the issue.

@matifali matifali closed this as not planned Won't fix, can't repro, duplicate, stale Apr 15, 2024
@matifali matifali mentioned this issue May 2, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
waiting-for-info The issue creator is asked to provide more information.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@matifali @yoshi23 @MrPeacockNLB @elliot-graebert-skydio