-
Notifications
You must be signed in to change notification settings - Fork 217
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
authenticate_on_every_request and Gateway #13
Comments
So is this just me or is this the expected behaviour? |
This is what the current implementation does, and I agree that it is far from optimal. I'll plan on fixing it for the next release, but I don't know how soon that will be. Feel free to submit a patch with tests if you like. |
Hi I now understand better why its doing what it does, it is kinda an optimisation problem. If there is no ticket in the session then no point going to CAS server to be told that when on a Gatewayed page, just wasn't sure if there is anything I am missing in doing this. I find the CAS protocol rather confusing, mostly due to poor documentation. I am having a load of stability/deployment issues with rubycas server, and looking/forced to write my own version from scratch using node.js or move to a different protocol. So cannot commit to fixing this issue until server/protocol problems are resolved. Cheers, |
Well, for anyone looking for a quick fix, you can override this behaviour in your Rails application by creating a new file in
|
Hi, I used 'authenticate_on_every_request' its keep authenticate with server but while sending a post request to server with parameters, after authentication of this request am not getting the post method parameters. i don't know why ? Regards |
If using the gateway filter a request is made for every action, even though authenticate_on_every_request is set to false.
Not sure if this is necessary for the protocol (I don't think so), but obviously this has serious performance issues for us.
Cheers,
Jim.
The text was updated successfully, but these errors were encountered: