-
Notifications
You must be signed in to change notification settings - Fork 72
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
Issue with fallback on in_memory with http basic #52
Comments
It's a general Symfony security question, and not directly related to lightsaml... but from the top of my head, you could try with custom entry point, or customer authentication handler... Maybe it would be better to ask for symfony support on it. |
Hi @tmilos , thanks for the answer :) I posted here because I am getting this issue only when using this bundle and related provider :) I will keep you updated, in the meantime let me know if you have any ideas about that :) thanks |
Could you post an example of working fallbacks, so I could debug and find what's different in this case? |
Sure! Here's what I've done: Test 1 - Working I used a chained provider with the default FOSUserBundle provider as chain first element, and the "in_memory" provider as second. I can post an example snippet if you want, but it's just a basic chain provider. If I go to a route that is protected by the firewall, If I am logged with the FOSUserBundle User I can access to it without issues. Otherwise, the basic auth dialog is prompted. Test 2 - Not Working I used this bundle and the two ways I have to declare a fallback are not working. Way 1: use the chained provider in the default config for the bundle, like this:
This is not working. Way 2: the example I pasted up here. The symfony docs says that I can specify a fallback http basic auth in that way, by adding an "http_basic" element to the config. This is also not working. As told before, I wrote here because I am experiencing this issue only with this bundle :( Thanks |
@francescomalatesta did you find a solution to this ? I have the same problem |
Hi guys,
I am working with your component and I have a specific necessity.
I want to use an SSO service with your package, but I also want to use the in_memory default symfony solution as a fallback.
I tried to use a chained provider and also tried to specify the fallback like this:
It doesn't work, I just continue being redirected to the login page. How can I make it trigger the in_memory provider as a fallback? Thanks
The text was updated successfully, but these errors were encountered: