f21e24ffc2
We do it this way round so that only the "owner" can delete the access token (i.e. `/logout/all` by the "owner" also deletes that token, but `/logout/all` by the "target user" doesn't).
A future PR will add an API for creating such a token.
When the target user and authenticated entity are different the `Processed request` log line will be logged with a: `{@admin:server as @bob:server} ...`. I'm not convinced by that format (especially since it adds spaces in there, making it harder to use `cut -d ' '` to chop off the start of log lines). Suggestions welcome.
|
||
|---|---|---|
| .. | ||
| ui_auth | ||
| __init__.py | ||
| _base.py | ||
| account_data.py | ||
| account_validity.py | ||
| acme.py | ||
| acme_issuing_service.py | ||
| admin.py | ||
| appservice.py | ||
| auth.py | ||
| cas_handler.py | ||
| deactivate_account.py | ||
| device.py | ||
| devicemessage.py | ||
| directory.py | ||
| e2e_keys.py | ||
| e2e_room_keys.py | ||
| events.py | ||
| federation.py | ||
| groups_local.py | ||
| identity.py | ||
| initial_sync.py | ||
| message.py | ||
| oidc_handler.py | ||
| pagination.py | ||
| password_policy.py | ||
| presence.py | ||
| profile.py | ||
| read_marker.py | ||
| receipts.py | ||
| register.py | ||
| room.py | ||
| room_list.py | ||
| room_member.py | ||
| room_member_worker.py | ||
| saml_handler.py | ||
| search.py | ||
| set_password.py | ||
| state_deltas.py | ||
| stats.py | ||
| sync.py | ||
| typing.py | ||
| user_directory.py | ||