-
Notifications
You must be signed in to change notification settings - Fork 74
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
How to configure BeSimpleSsoAuthBundle #48
Comments
you should at least set up one access_control in your security.yml, Please check this http://symfony.com/doc/current/book/security.html |
Sorry, I forget to put. I still have the problem. Thanks! |
I was having a similar issue with a 2.2 project. I decided to start with a fresh 2.3 project to see if I could get it to work. The state I'm in now is that I login on CAS form and then am redirected to /login on my application. I was getting a "admin" user does not exist warning on that login screen even though I was already authenticated with CAS. That was solved by adding the "in_memory" provider as you see below. Clearly, I'll need to implement a new provider. But, I still have one big question: Do we have to implement a login action? If so, what logic should be there? I have the following security.yml:
And then in my routing.yml:
|
I'm trying to use this bundle in a project but it is giving me some problems.
I create this memory providers because if not i get this error message:
Then when i access to /backend it redirect to login URL: https://cas.XXX.com/ID/login, up here all right! but when I start session it redirect to:
/backend/login_check?ticket=ST-1383036359rD96A55DD1B77B754D4
and i have a Exception
I know thats is because of the "?ticket=ST-1383036359rD96A55DD1B77B754D4" but i dont know how to solve.
thanks!
The text was updated successfully, but these errors were encountered: