Bug 25390 - Login box is removed from opac-main.tt if Shibboleth or CAS is enabled
Summary: Login box is removed from opac-main.tt if Shibboleth or CAS is enabled
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: OPAC (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Owen Leonard
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-05-06 15:46 UTC by Lucas Gass (lukeg)
Modified: 2025-02-10 15:15 UTC (History)
2 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments
Screenshot showing proposed form update (42.54 KB, image/png)
2025-01-25 17:14 UTC, Owen Leonard
Details
Alternate proposal (42.34 KB, image/png)
2025-01-25 17:15 UTC, Owen Leonard
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Lucas Gass (lukeg) 2020-05-06 15:46:36 UTC
On the OPAC main page (opac-main.tt) if CAS or Shibboleth are enabled than we remove the login box on the right side of the page (#login). I am wondering if this is necessary:

1. It does not remove local login functionality as you can still login via the modal in the top right corner.
2. In multi library systems this can be a problem as some might use a SSO service while others would like to see the login box on the right side.
3. Maybe it would be simpler to keep the login box regardless of sign in method and hide it via CSS for libraries that don't want it?
Comment 1 Katrin Fischer 2020-05-06 21:46:33 UTC
I think the reasoning was that when you have a lot of different authentication methods activated they would clutter up the right column. Or the user would not find the Shibobleth/CAS options as they asssume they have to enter it there (where the other links don't show).

Hope that makes sense.
Comment 2 David Cook 2023-04-26 01:17:00 UTC
(In reply to Lucas Gass from comment #0)
> 3. Maybe it would be simpler to keep the login box regardless of sign in
> method and hide it via CSS for libraries that don't want it?

This is my inclination. Some libraries want both local login and SSO, while others don't. CSS is the easiest way to control this on a per-instance basis.

Bug 31064 was designed to make it easier to control the display of the local login.

That said, it looks like there are quite a few lines like "<p>If you do not have a Google account, but do have a local account, you can still log in: </p>" which are missing selectors at the moment...
Comment 3 David Cook 2024-12-06 00:01:04 UTC
Is this one still valid? 

I don't use CAS or Koha's Shibboleth implementation... just OpenID Connect and other mechanisms
Comment 4 Laura Escamilla 2025-01-24 18:22:06 UTC
(In reply to David Cook from comment #3)
> Is this one still valid? 
> 
> I don't use CAS or Koha's Shibboleth implementation... just OpenID Connect
> and other mechanisms

Yes this is still valid.
Comment 5 Owen Leonard 2025-01-25 17:14:22 UTC
Created attachment 177144 [details]
Screenshot showing proposed form update

It sounds like what we want is to show all login options unless 'opacShibOnly' is true?

The attached screenshot shows updated buttons (making the Google button consistent with buttons for custom identity providers) and a generalized note to be shown if OAuth and/or other identity providers are enabled.

I think we could even simplify the hint further:

"If you have a local account you can log in below"
Comment 6 Owen Leonard 2025-01-25 17:15:46 UTC
Created attachment 177145 [details]
Alternate proposal

Here's a different version which follows other examples I've seen on the web.
Comment 7 Laura Escamilla 2025-02-10 15:15:15 UTC
(In reply to Owen Leonard from comment #6)
> Created attachment 177145 [details]
> Alternate proposal
> 
> Here's a different version which follows other examples I've seen on the web.

I like the alternative proposal, Owen. Many libraries like this style of login.