-
Notifications
You must be signed in to change notification settings - Fork 281
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
Implement SSO #962
Comments
SSO is on the roadmap, but we are not working on it yet. We would likely start with Google as login provider, followed by GitHub. If you have feature requests for paid organizations it is best to send them to [email protected], that will help us prioritize what to work on, for example which login providers to support first. |
Can I tackle this one (with GitHub)? |
@v0idpwn Any help with this issue would be greatly appreciated but to avoid any wasted effort we should discuss how we plan to implement it. Feel free to reach out to the Hex team at #elixir-lang on Freenode or the Hex channel on the Elixir Slack and we can discuss it there. |
I think the name of the issue is a bit confusing, Single Sign-On (SSO) is a more broad topic and is usually related to being able to use your own identity provider of choice. The low-hanging fruit here would be simply using Github / Google Oauth to register / log in users, which would greatly benefit the user experience in my opinion. |
Hello,
We already use the hexpm and would like to have more control over how our users have to access our org at hexpm. With that, I like to know If has any plan to implement SSO so we can integrate with Azure AD, Google, and others.
I don't know if is the best way to ask about that, sorry if not.
The text was updated successfully, but these errors were encountered: