Closed GoogleCodeExporter closed 9 years ago
Original comment by jaim...@gmail.com
on 17 Feb 2014 at 11:29
Hi Yorn!
I'm afraid this is not an issue introduced at any point, but something that has
never worked. The fix you are referencing to is basically a quick fix to allow
basically *some* kind of logout, but not a complete SLO.
I've been discussing this briefly with Olav, and there's no easy way to solve
it, because there's no way to trigger SLO from the authorize module. A possible
approach would be that both the IdP and SP register their own logout handlers
in the state array, and then let the authorize module use that handler to
initiate a SLO. It would be possible then to initiate SLO regardless of where
you are using the module (right now you get no logout link if you are on the
SP, for instance), but that's also a non-negligible amount of work, and we've
decided that it can wait until 2.0.
Original comment by jaim...@gmail.com
on 18 Feb 2014 at 12:47
As a workaround, would it be possible to add a module configuration parameter
to send the user somewhere else than the simpleSamlPhp installation page?
Also, I wonder how this is fixed in Feide; when I log in with my NTNU account
and then try to visit a UNINETT service, I get a button that allows me to log
in as another user.
Original comment by yorndej...@gmail.com
on 20 Feb 2014 at 12:20
Original comment by jaim...@gmail.com
on 26 Feb 2014 at 2:45
Closing the issue here, moved to:
https://github.com/simplesamlphp/simplesamlphp/issues/53
Original comment by jaim...@gmail.com
on 27 Feb 2014 at 7:21
Original issue reported on code.google.com by
yorndej...@gmail.com
on 11 Feb 2014 at 11:54