-
Notifications
You must be signed in to change notification settings - Fork 32
Conversation
Deploying matrix-authentication-service-docs with Cloudflare Pages
|
3f30498
to
6c0effd
Compare
b425f9b
to
7526713
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just one comment really (but applies to all filters), rest looks sane
let (sql, arguments) = Query::update() | ||
.table(CompatSessions::Table) | ||
.value(CompatSessions::FinishedAt, finished_at) | ||
.and_where_option(filter.user().map(|user| { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should the CompatSessionFilter
be responsible for constructing its own WHERE
clauses? I am a bit concerned we'd forget to update this code here if we added more to the filter
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did think of this, but it was annoying in particular for the compatibility sessions, as when we query, we JOIN
on the compat_sso_logins
and filter on that, which we can't do for updating the finished_at
field.
I'll have a shot though in another PR
7526713
to
21ed451
Compare
This is reviewable commit by commit.
On top of #2970
mas-cli manage kill-sessions
finish sessions in bulkThis makes it so that when we finish sessions (like when deactivating a user), we can do that in bulk.
This introduces new APIs on the three repositories, which are then used by the
mas-cli manage kill-sessions
command.The reason we need this, is so that we can kill all sessions when a user is deactivated, so that they don't leave active sessions behind, and don't get magically logged in once we reactivate them.