-
Notifications
You must be signed in to change notification settings - Fork 62
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
Problem with multple servers #112
Comments
Can you elaborate a bit more on what you mean by having the "strategy set"? And why they are not all similar? |
I have two routes: In this route I create and set the strategy dynamically because some parameters are send from another api. My second url: This is the callback url. The exception Unknown authentication strategy is thrown in this line: passport.authenticate('strategy name', function()). I think this happens because the callback url is being called in a server other than the one the strategy was initially set. |
Are you using some sort of in-memory state storage? |
We are using redis. |
This sounds like a configuration issue in how you're selecting the strategy based off the information I have here. |
@machuga The flow starts by calling the /auth/adfs passing the parameters. Then after the user enter user and password the callback are called by the adfs. |
Have you verified the other machines still have these query params available? |
They don't have it. Because the strategy is set inside a route. |
In my production environment we have 3 servers. When I set a strategy in one of them, when the redirect comes it may go to a server where the strategy was not set causing the Unknown authenticate strategy error.
How can I solve this problem?
The text was updated successfully, but these errors were encountered: