-
By the way, is there a way to somehow convert user account from "Builtin User Store" to "External Authenticator"?
-
This looks like a rare case for ordinary use, and will not be implemented. Nevertheless, you may change user audit source by selecting them and click the operations menu from user management page.
-
Thank you for your response. Functionality to convert user from builtin to external authentication is sufficient solution.
However, the use-case described is not that rare. Many of our customers prefer to manage their workforce from one central place, whereas accounts for customers or "outsiders" can be self-created in the OneDev system.
-
Name Previous Value Current Value Type
Question
Improvement
-
OneDev
changed state to 'Closed' 1 year ago
Previous Value Current Value Open
Closed
-
State changed as code fixing the issue is committed (247390d4)
-
OneDev
changed state to 'Released' 1 year ago
Previous Value Current Value Closed
Released
-
State changed as build OD-5603 is successful
| Type |
Improvement
|
| Priority |
Normal
|
| Assignee | |
| Labels |
No labels
|
We host many open source projects on OneDev system and therefore we allow open registration for community users and "Auth Source" for these users show "Builtin User Store". And this us correct.
However, for our team members we manage accounts externally and for our team "Auth Source" shows "External Authenticator" which is also correct.
The problem is, that some team members create their accounts directly in OneDev before they are created on our external system. And this is a significant problem for us, because then we can not longer manage their accounts on our external system.
Ideal solution for us would be to restrict self-registration for users based on their email domain. To be more specific, we would like to allow self-registration for users with emails that are not in our company domains.
Is there a way to restrict user registration in such a way? If not, is there a chance to have something like this in future versions?