Wiki: Default Authentication strategy on Login page

[seafre]

Describe the bug
"...the default Local strategy cannot be disabled as it is required for root administrator login" which results in a non-intuitive user experience at login.

Administrator should be able to select the "Primary/Default Authentication strategy".

To Reproduce
Steps to reproduce the behavior:

1. Configure new Auth strategy
2. Login page

Expected behavior
The username/password prompt should be replaced with, as an example, "Sign in with [GitHub Enterprise]" as the main login item.

This decreases the user's likelihood they attempt to use another user/password to gain access, and the Local is shown only under "or login using..." because this is always required.

Screenshots

[githubdave2020]

I had to walk nearly every user through this same situation. It should be prioritized!

[signalkraft]

In my case I wanted users to always pick Keycloak and I wanted to avoid showing the regular login form altogether. Accomplished this with a simple rewrite rule from /login to /login/keycloak (in our case in Helm on Kubernetes):

[...]
      - ingress:
          tls: true
          annotations:
            nginx.ingress.kubernetes.io/configuration-snippet: |
              rewrite ^/login$ https://{{ requiredEnv "HOSTNAME" }}/login/keycloak redirect;

Works like a charm, users don't even see the login screen anymore. Obviously give your SSO user admin access first, you won't be able to use local sign in anymore.

Hope this helps somebody in the meantime.

[michidk]

Thanks, @signalkraft! Exactly what I needed. This issue should definitly be prioritized.

[steviethecat]

Agreed, this should be prioritized. This issue has kept me from upgrading to version 2 for a while now.

[NGPixel]

This is already being addressed in 2.5.

[nebulade]

This is already being addressed in 2.5.

This is great news, as we get this confusion from our users ( Cloudron ) often as well. Is there a way to track the task for 2.5 somewhere?

[Smankusors]

This is already being addressed in 2.5.

This is great news, as we get this confusion from our users ( Cloudron ) often as well. Is there a way to track the task for 2.5 somewhere?

it's documented on here. But it seems he missed the deadline though. 😞