[GH-ISSUE #24] SSO authentication #23

Open
opened 2026-02-27 23:18:32 +03:00 by kerem · 1 comment
Owner

Originally created by @kitzin on GitHub (Jul 17, 2018).
Original GitHub issue: https://github.com/snibox/snibox/issues/24

It would be nice to have some single sign on authentication like CAS or SAML2 to add this application to an existing environment.

Originally created by @kitzin on GitHub (Jul 17, 2018). Original GitHub issue: https://github.com/snibox/snibox/issues/24 It would be nice to have some single sign on authentication like CAS or SAML2 to add this application to an existing environment.
Author
Owner

@zjzeit commented on GitHub (Jan 27, 2019):

Second! Also possibly an http-header authentication (where only a username header is needed). I use nginx to authenticate my services, and simply pass the user header to the service which returns session info.

<!-- gh-comment-id:457950637 --> @zjzeit commented on GitHub (Jan 27, 2019): Second! Also possibly an http-header authentication (where only a username header is needed). I use nginx to authenticate my services, and simply pass the user header to the service which returns session info.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
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
starred/snibox#23
No description provided.