-
Notifications
You must be signed in to change notification settings - Fork 222
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support for multiple client_id #968
Comments
The idea is to use one oidc-client-ts instance per client-id/idp... |
Sure, but how to manage the callback? I don't want to have one callback page per client id. This is why I add a query string to the callback url. I wonder if there would be a better mean |
Sound good, without a special query string, you could search through the temporary states created by this library to find out which client-id instance is used... oidc-client-ts/src/OidcClient.ts Lines 149 to 156 in 2879261
What do you mean by "two microfrontends", currently there is an issue with multiple tabs open. There is no locking implemented yet... See #430 |
This issue (question) staled, closing it for now. |
Hello,
I need to be able to support multiple client_id (and potentially multiple OP) used by multiple microfrontends loaded in the same page. I didn't found that use case to be taken into account. However in the storage the key contains the client_id. So I probably didn't understood the intention.
In order to do so I created a wrapper around UserManager. The wrapper receives the client_id to be used and set it in the config.
The iFrame should know about the client_id so I pass it as a query parameter:
In the callback pages I then do the following:
This actually works but I wonder if there would be a better approach.
Regards,
Serge
The text was updated successfully, but these errors were encountered: