Future of Web API Login OpenID Connect or plain OAuth 2.0

[drpeterson]

Is OpenID Connect on Steam's radar since OpenID Connect is what will be used going forward. I use Keycloak for centralized security and they only support adding providers that implement OpenID Connect. For that to work I need an Authorization Url, a token Url, a Client ID and a Client Secret. From what I can tell Steam still uses OpenID2.0. OpenID 2.0 is deprecated. Is it possible to use OpenID Connect to allow users to login with steam to 3rd party sites? I see Steam began work on an OAuth 2.0 api but that seems to be gone as well. My preference would be to have Steam upgrade to OpenID Connect. Is there any word on this?

[McJuicy | Brain DEAD]

Has this been answered yet?

[Phoenix_ZA]

+1
I'm implementing steam login now and I have to use 'official' libraries that have long since been left unsupported.

[MAurelius24]

+1 Steam upgrading to OpenID Connect would literally be the greatest thing to happen to me this month. I've been staring at nodejs providers trying to frankenstein the plain OAuth2.0 endpoint into a custom implementation and my brain hurts...