Support SAML and OAuth2 logins as consumer #236

Closed
opened 2020-04-30 12:17:13 +02:00 by nik · 10 comments
Owner
No description provided.
Author
Owner

changed title from Support S{-MA-}L and OAuth2 logins as consumer to Support S{+AM+}L and OAuth2 logins as consumer

changed title from **Support S{-MA-}L and OAuth2 logins as consumer** to **Support S{+AM+}L and OAuth2 logins as consumer**
Owner

We should also support Kerberos.

We should also support Kerberos.
Author
Owner

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.

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.
Owner

created merge request !1946 to address this issue

created merge request !1946 to address this issue
Owner

mentioned in merge request !1946

mentioned in merge request !1946
Author
Owner

removed milestone

removed milestone
Author
Owner

unassigned @debdolph

unassigned @debdolph
Author
Owner

assigned to @debdolph

assigned to @debdolph
Owner

mentioned in merge request !2058

mentioned in merge request !2058
Owner

mentioned in commit 6ca32fa347

mentioned in commit 6ca32fa3478a9f5a9060f9b528bc134ec28a73f6
Sign in to join this conversation.
No milestone
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
aleksis/AlekSIS-Core#236
No description provided.