Skip to content
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

Avoid conflicts with other OIDC flows #1250

Open
Chiyo-no-sake opened this issue May 17, 2024 · 1 comment
Open

Avoid conflicts with other OIDC flows #1250

Chiyo-no-sake opened this issue May 17, 2024 · 1 comment
Labels
question Further information is requested

Comments

@Chiyo-no-sake
Copy link

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?

@pamapa pamapa added the question Further information is requested label May 17, 2024
@pamapa
Copy link
Member

pamapa commented May 17, 2024

Check

skipSigninCallback?: boolean;

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants