OIDC Support

[Dedric F]

Having OAuth is pretty slick and definitely useful but I'm curious if you've looked at or would be willing to add OIDC (OpenID Connect) on top of the auth system?

The main driver for me is that the OIDC setup would allow for quicker tool integrations versus having to customize the OAuth2 config process for each tool BUT most low/no-code external tools come with OIDC setup out of the box.  The OIDC system is effectively (i'm over-simplifying for sure) a "rosetta stone" translating the OAuth2 endpoints, required fields, etc into well known variables.

So instead of calling "user.sportsengine.com/oauth/authorize" the external tools fetch the OIDC config, parse it and then just call the $authorization_endpoint as a variable.  So much easier to code the general OIDC case versus building specifics for each OAuth2 provider

 

For reference here's hte OIDC specification:  Final: OpenID Connect Discovery 1.0 incorporating errata set 2