Multiple Point Client about openid-connect-java-spring-server HOT 3 CLOSED

Further: ideally, the account chooser setup would let the client speak off-the-shelf OIDC without special parameters; this needs to be investigated as well.

from openid-connect-java-spring-server.

Codification of new plan (from initial discussions):

The client would call the account chooser to effectively perform the discovery process on its behalf.

User starts at client app, protected by this filter
Filter Account Chooser transaction configured Account Chooser endpoint (AC), includes callback uri and client id
AC gives user multiple options for login against different connect servers
AC redirects user back to client app indicator as to which server the user chose (the OpenID Connect Issuer)
Filter sends catches redirect and plucks issuer off
Client looks up issuer's configuration information (ether preconfigured or through further discovery) and begins a vanilla OIDC transaction with the IdP

from openid-connect-java-spring-server.

I didn't pass the client_id because to me this identifier is worked out between the OIDC Server and the Client. The Client could come to the OIDC Server with a client_id in mind, but the OIDC may already have an existing, but different Client with that same identifier. When one adds multiple OIDC Servers this increases the odds of a conflict occurring. So, I coded with the client_id being a parameter of an OIDC Server configuration along with the client_secret, authorization endpoint URI, et cetera to remove the potential for this problem to occur.

from openid-connect-java-spring-server.