Personal Sessions: add create, list, get, revoke Admin APIs #5141
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Follows: #5106
Part of: #4492
This PR introduces some admin API endpoints for Personal Sessions.
Future:
Open question/thought I have: It seems like it would be good to bundle information about the active access token for each session, in the get and list endpoints.
For instance, I might want to filter on 'sessions with expired access tokens', or I might want to see the expiry time at a glance in the session list, or even sort by that time.
Wondering what your thoughts are on exposing that?
Should the relevant access token be embedded in
attributes
as a nested object?: