# Improve GitHub login for private sites **URL:** https://meta.discourse.org/t/improve-github-login-for-private-sites/44836 **Category:** Feature **Created:** [May 26, 2016, 1:04pm UTC](https://meta.discourse.org/t/improve-github-login-for-private-sites/44836 "2016-05-26T13:04:34Z") **Posts on this page:** 1 **Showing post:** 2
### Author: ![erlend\_sh](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/erlend_sh/32/119475_2.png) [@erlend\_sh](https://meta.discourse.org/u/erlend_sh) #### Post date: [May 26, 2016, 4:09pm UTC](https://meta.discourse.org/t/improve-github-login-for-private-sites/44836/2 "2016-05-26T16:09:16Z")
Those solutions sound quite complicated. Have you seen similar functionality in any other web app? What if you had to sign up with your whitelisted email, but you could still connect with your GitHub account post-registration; might that suffice? > [@Ability to connect with OAuth providers when user is registered?](https://meta.discourse.org/t/ability-to-connect-with-oauth-providers-when-user-is-registered/42457): > > Some OAuth2 providers don’t provide email thus user have to fill the form to login. After filling out the signup form, a new user will be created and connected with this provider. But that situation hurts when a user have been registered, it can’t connect with this OAuth2 provider. In particular, a customer comes to me for building a integration with an external service for Discourse. Therefore, I am willing to have a way to let user connect with a Oauth2 provider in the user settings as well … --- _[View the full topic](https://meta.discourse.org/t/improve-github-login-for-private-sites/44836)._