https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23930
David Cook <dc...@prosentient.com.au> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dc...@prosentient.com.au
--- Comment #4 from David Cook <dc...@prosentient.com.au> ---
I'm not sure that I understand this one.
What SSO are you targeting and what scenario?
From the OPAC side, I have a OpenID Connect client for Koha (which one of these
days I'll find time to upstream). If I already have a session with the Identity
Provider and I click on a Koha link, it'll prompt me to log in, I'll choose my
Identity Provider from the login options for Koha, it'll bounce me to the IdP,
then bounce me back. If I don't have authorization/permission, I'd expect to
see my original Koha page saying that I'm not authorized.
I could see it being an issue if it re-directed me to a login page though, as
I'd already be authenticated just not authorized...
...which is where I'm getting lost with your description.
You're saying the patron has been authenticated but they're not authorized to
be in the staff client, so they're being re-directed to the Koha login page
instead of whatever page they were trying to access?
I take it that you want to redirect the patron back to the page they were on
before they navigated to Koha?
What kind of SSO is this? I'm guessing the redirection to the IdP must be
automatic and not require the user to click on something on the Koha staff
client login side?
--
You are receiving this mail because:
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list
Koha-bugs@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
