GitHub as OAuth service provider: Is anybody using this productive ?

[Rollo62 498]

Hi there,

 

so far I have not considered GitHub as an OAuth service provider, also usable for external, productive apps, but this rough idea came always into my mind since some time.

So I wanted to check now if and how that could be possible.

The info about terms and conditions is a little unclear to me, about that OAuth Application from GitHub:

https://docs.github.com/en/developers/apps/building-oauth-apps/creating-an-oauth-app

https://membrane-soa.org/service-proxy-doc/4.2/oauth2-github.htm

https://docs.readme.com/docs/setting-up-github-oauth

 

I assume that a GitHub account >= Pro, can be used as a normal OAuth-Service provider, also for external apps not hosted on GitHub itself.

Since I cannot find a lot information about these terms, I am very unsure if this is a good idea, or recommended only for development purposes.

Who is using such already in productive applications ?

 

What I can see that GitHub allows up to 100 OAuth services, and I see no difference especially for development or production.

Are there special hidden costs, when using this productive, or is this all in the flat cost of the account ( which would starting from a Pro account at 4 USD/month, including up to 100 OAuth applications  ) ?

Are there special terms that forbid such kind of usage, outside the scope of GitHub projects ?

Are there any technical restrictions that may bite me in a productive system ( any resources/packages occupied per app, performance, access limits, transfer limits, or the like ) ?

 

If that is all OK, I think this would mean that GitHub is a very cost effective OAuth provider, only I cannot really believe that.

 

Maybe somebody here has experiences with using GitHub as service provider, and would like to give some tips and and share recommendations ?