Support SAML and OAuth2 logins as consumer

added part::backend type::feature workflow::confirmed labels

changed title from Support SMAL and OAuth2 logins as consumer to Support SAML and OAuth2 logins as consumer

We should also support Kerberos.

I am not in favour of supporting Kerberos directly. There are quite a few approaches:

• To authenticate passwords against Kerberos, use the LDAP SASL proxy scheme to load it off to slapd, or use PAM (feature request to support PAM logins is open)
• To support GSSAPI, rather use the RemoteUserBackend and load authentication off to the webserver, which will provide an HTTP header with the authenticated username

Directly supporting Kerberos is quite complex, and in my opinion does not provide any benefits, so having the user running AlekSIS get a service token and keytab is an unnecessary risk where security can also be handled by components further down the stack.

created merge request !301 (closed) to address this issue

mentioned in merge request !301 (closed)

removed milestone

unassigned @debdolph

assigned to @debdolph

mentioned in merge request !413 (merged)

added 1 deleted label

added board::todo label and removed 1 deleted label

added board::ready label and removed board::todo label

closed with merge request !413 (merged)

mentioned in commit 6ca32fa3