mirror of
https://github.com/anonaddy/anonaddy.git
synced 2026-04-25 22:25:55 +03:00
[GH-ISSUE #255] [Feature Request] SAML / Oauth SSO capabilities and User Provisioning (SCIM) #786
Labels
No labels
bug
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/anonaddy#786
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @timomayer on GitHub (Jan 12, 2022).
Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/255
To use AnonAddy in a corporate environment it would be necessary to provide SAML or OAuth connection and SCIM support for user provisioning. Can maybe done by using: https://simplesamlphp.org/
@alexanderadam commented on GitHub (Jun 12, 2022):
May I ask why you closed this issue?
Is something like OpenID Connect/OAuth already supported?
The Docker container doesn't seem to indicate OAuth related environment variables.
@willbrowningme commented on GitHub (Jun 16, 2022):
@alexanderadam I believe because it is a duplicate of #248
I'm afraid I do not have any plans at this time to implement SSO.
@disconn3ct commented on GitHub (Jun 18, 2022):
I understand the conflict with the paid service, but fwiw my use case for SSO (via oidc, keycloak) is far from corporate. I just run services for family, and the fewer passwords to remember (and 2fa and logins and site addresses and..) the easier my life is by far 😄 SSO means not having to keep a (corporate) checklist by my computer for password rotations, etc.