Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

As an application provider, I want to signal SRAM when a user logs in (not SAML/OIDC), so the collaboration and user are kept active #1719

Open
FlorisFokkinga opened this issue Dec 2, 2024 · 0 comments

Comments

@FlorisFokkinga
Copy link
Contributor

FlorisFokkinga commented Dec 2, 2024

To not retain PII unecessarily, SBS suspends and removes collaborations that haven't been used to log in to an application for a year.
SBS only knows about logins to applications if SAML or OIDC is used. For example: if an application uses LDAP and users log in using an SSH key, SBS doesn't know about logins. Editing a collaboration also marks them active for a year.

I suppose the question here is if, and under what conditions, we want to trust applications to mark collaborations active.

@FlorisFokkinga FlorisFokkinga converted this from a draft issue Dec 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: New
Development

No branches or pull requests

1 participant