Do you plan on supporting multiple providers at some point? Easiest example of this would be the various social medias (Sign in with X - google, facebook, github, etc..), where you have a choice of your provider.
In an enterprise world, this may be various Client's Identity Providers (Multi-Tenancy) and your own internal employees IdP.
Can you give some extra informations ?
keycloak seems to be a complete user suite of tools. It does not seems to come as a simple oauth client library that can manage multiple identity providers ...
Thanks for the feedback. I've checked the link you've sent.
I think we're talking about a different use case here.
With angular-oauth2-oidc, we can easily get an authentication mechanism between an angular application and a third party identity provider directly (with no use of extra custom authentication server). It is the angular application that is in charge of displaying a login page (with a social login button for example) and calling the identity provider for authentication (implicit grant type flow).
With Keycloak, angular is not in charge of the authentication process anymore. It is the Keycloak server that is in charge of doing all the job.
Personnaly, I would be interested in having angular-oauth2-oidc with several identity providers ...
Currently, there are no plans for this. I personally would use an identity server that delegates to several other login provierders and maps their tokens to a common token structure for the application.