Multiple Identity Providers support.

[mnaveed1842]

Hi Team
Currently we are relaying on the angular-oauth2-oidc mechanism for the authentication but we need to support JWT support as well for the use case 2.

Use Case 01:
User enter the username and password and can login to the application and for this use case we are using angular-oidc authentication mechanism.

Use Case 02:
Our application is redirected using URL from other application. So the idea is that the destination application will send us only the JWT token to our backend once the verification part is done at our backend we will allow the user to login with providing username and password.

The questions is is there a possibility the token we received which does not have username and password.It only contains the userId. Can we use our existing angular-oidc authentication mechanism?
OR we need to have JWT implementation as well in parallel?

Your support will be appreciated

[jeroenheijmans]

I'm not entirely sure what you're asking, perhaps there's a small language barrier... could you explain a little further what the bug or issue is you're running into?

The library supports most notably Auth Code + PKCE flow, which is a redirect flow where you enter your credentials at the IDS. It will then typically send you back to the Angular app that can than get the access token for you (and Keycloak can decide to make that access token a JWT token).

The Implicit flow is similar and also still supported. The deprecated Resource Owner Password flow is also still in the code base, but you should consider it legacy and avoid using it under most circumstances.

[mnaveed1842]

@jeroenheijmans thanks for your Input. I have added more info to my question.

[jeroenheijmans]

I've reread your original post, but alas, I personally don't fully understand it. But perhaps someone else from the community can chip in?

Regardless, you say "need to have JWT implementation as well": what may be helpful to know is that JWT stands for "JSON Web Token", and it merely describes a way to put meaningful data inside an access or id token. Often it is used in conjunction with OpenID/OAuth2, and this library will support that, where the redirect flows are used and the final tokens are JWTs.

But other than that, I'm not entirely sure what the question is. Again, perhaps someone else can chip in?