EOS and OpenID w/ external Auth

Development Programming & Scripting
, ,
1

I’m unclear on how the login flow is supposed to work with OpenID, OSSv2 and EOS and was hoping for some clarification.

My understanding of the intended flow is:

  1. On startup, the client requests to autologin
  2. Under the hood, using the AuthOSSAdapater, the client authenticates with our proprietary Identity Provider
  3. After that succeeds, through the AuthOSSAdapter, the client calls “GetLinkedAccountAuthToken”.
    1. The proprietary Identity provider implements this and retrieves a JWT Token?
  4. The JWT Token is used to create an ExternalAuthToken, which is then passed back to AuthOSSAdapater, which then uses it as part of the EOS connect login?
  5. On the EOS developer portal, we add the Identity Provider OpenID with a corresponding URL to verify that the token is correct
  6. If the token is correct, EOS responds with the login status

Is that correct?

As a further question, are we supposed to parse something out of the JWT Token or pass it back in its entirety?

[Attachment Removed]

2

Yes, this is correct, and you simply need to pass the JWT token to EOS as is, which our backend will verify.

In general, EOS has a two-stage login workflow: firstly, the stable identity provider (OpenID, console platform, Epic, etc.), and then, the EOS Game Services backend (Connect).

[Attachment Removed]