You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be awesome to have some other authentication options for the ZROK Controller login webpage.
I checked the docs and did not really see anything, but some low hanging (possible) fruit:
Email only magic link. No passwords! This would actually work in a lot of my use cases. It would be pretty secure in our environment and I wouldn't have to create and distribute passwords to anyone (When I know they arent going to remember it anyways!)
HTTP Header auth - A lot of tools (caddy-security, 0Auth, Authelia, Apache Mellon, etc...) can set special header values when authentication is successful. In Caddy-Security's option, when using OIDC it uses X-Token-User-Email. The login should check for this value, and assign the user based on this value. If the user does not exist, go ahead and create the user.
Of course, LDAP, OIDC, SAML, etc.... but those would probably require more intense changes to the code.
The text was updated successfully, but these errors were encountered:
It would be awesome to have some other authentication options for the ZROK Controller login webpage.
I checked the docs and did not really see anything, but some low hanging (possible) fruit:
Email only magic link. No passwords! This would actually work in a lot of my use cases. It would be pretty secure in our environment and I wouldn't have to create and distribute passwords to anyone (When I know they arent going to remember it anyways!)
HTTP Header auth - A lot of tools (caddy-security, 0Auth, Authelia, Apache Mellon, etc...) can set special header values when authentication is successful. In Caddy-Security's option, when using OIDC it uses X-Token-User-Email. The login should check for this value, and assign the user based on this value. If the user does not exist, go ahead and create the user.
Of course, LDAP, OIDC, SAML, etc.... but those would probably require more intense changes to the code.
The text was updated successfully, but these errors were encountered: