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.

Sign up for GitHub

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

Jump to bottom

Access tokens are not invalidated when credentials are invalidated via an external auth provider #4158

Open
matrixbot opened this issue Dec 16, 2023 · 0 comments
Open

Access tokens are not invalidated when credentials are invalidated via an external auth provider #4158

matrixbot opened this issue Dec 16, 2023 · 0 comments
Labels
Security T-Enhancement z-p2

Comments

@matrixbot
Copy link
Collaborator

matrixbot commented Dec 16, 2023 •
edited
Loading

This issue has been migrated from #4158.

If synapse is configured to interface with an external auth provider (such as LDAP), there is no mechanism for that external system to feed back to synapse if a user's credentials have been locked/revoked/etc. Synapse's access_tokens stay valid forever.

A related question: if a user's password is changed in the external system, should we require all matrix clients to log in again, as we would with a local password change? If so, how should this be implemented?
@matrixbot matrixbot changed the title Dummy issue Access tokens are not invalidated when credentials are invalidated via an external auth provider Dec 21, 2023
@matrixbot matrixbot reopened this Dec 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Security T-Enhancement z-p2
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@matrixbot