The user might be able to stay logged in the Environment even if he accesses different domains.
There are 3 reasonable solutions for
Centralized login and cookies distribution
Here is a good explanation of how this solution can be done: http://poocs.net/2005/10/2/multi-domain-single-signon
Here is a tutorial explaining part of its implementation: http://rubyglasses.blogspot.com/2009/12/rails-single-sign-on-with-rubycas.html
Couln't quite understand this solution. It seems like too much for what we need. Just in case, here is the link to the project: https://github.com/onelogin/ruby-saml
Although old, the cookies distribution article explains the basic idea involved in a sso feature without changing the authentication solution or using third-party server like rubyCAS.
Another good point involved in this solution is that it appears to be easier and less intrusive than setting a rubyCAS server, since rubyCAS requires the user to be redirected to the server to login. This is also seems to be the solution proposed by Terceiro in the last development meeting.
The task point estimation is done based on the first solution.
This feature is related to: ActionItem61
- 07 Feb 2011
some other actionitems comments' states this was already implemented, was it really?
- 25 Feb 2012
This AI was not implemented yet, it's pending.
Which actionitems comments are you talking about?
- 26 Apr 2012