You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When developing a front-end application that requires two or more IDPs (one being done even with another library), the library seems to conflict because it tries to manage code and state parameters that should be handled by another flow.
From what I've seen, this library handles OIDC's parameters also when they are sent to another route in the context provider, correct?
Is there a way to specify a specific callback url so that it only handles the flow when parameters are sent there?
If not, is there a workaround for this or a way to implement it?
The text was updated successfully, but these errors were encountered:
When developing a front-end application that requires two or more IDPs (one being done even with another library), the library seems to conflict because it tries to manage code and state parameters that should be handled by another flow.
From what I've seen, this library handles OIDC's parameters also when they are sent to another route in the context provider, correct?
Is there a way to specify a specific callback url so that it only handles the flow when parameters are sent there?
If not, is there a workaround for this or a way to implement it?
The text was updated successfully, but these errors were encountered: