-
-
Notifications
You must be signed in to change notification settings - Fork 932
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
GDPR compliance #1551
Comments
Our Matrix-server in question Privacy policy statement will contain (when done 100%) all the relevant info already, hence the traditional tickbox "I have read and accept the privacy policy statement" or to that effect is very enough regarding GDPR-part, shoiuld such be possible to do in Authentik registration flow. The "When", datetime field when accepted (successfully), again same adjacent Q. |
Which there currently doesn't seem to be support for. @olmari |
Signed-off-by: Jens Langhammer <jens.langhammer@beryju.org> #1551
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
... |
The main thing needed for this is a way for users to request all their data, maybe with Admin approval, the rest should mostly be doable with flows and custom stages, no? |
Correct, but I think the back channel log-out is also needed for this to invalidate users logins to Synapse for example? |
does synapse support back-channel logout? If it does that would greatly help with implementing it since I have found very few things that support it |
Apperantly not, matrix-org/synapse#11326 |
tbf authentik currently supports neither front-channel nor back-channel for OIDC, mostly because very few applications and libraries support it, so I haven't found a good reference implementation that I can test against/with (also I'm lazy) |
So when does the OIDC authenicated sessions expire currently? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@BeryJu You're yet to answer the question? |
Needs functionality to export all of a users data (available for admins) |
Describe your question/
Trying to figure out what are the requirements for GDPR complience, as an user needs to be presented/prompted for explicit concent to process their information.
Relevant infos
Public Matrix server, which is going to use Authentik as the user database/registry
This should probably also need an way to mark the user to have given their consent (and when), but they also need a way to withdraw it, even if that means deleting their account as a result.
The text was updated successfully, but these errors were encountered: