Session Revoke

Management revocation requires authenticated mTLS service identity and control.session.revoke (revoke_logins). Product-bound services may revoke only their own PRODUCT or CLIENT; tenant/project-bound services cannot revoke global login scopes. ADMIN_REVOKE closes derived state and records fixed old sid notifications and snapshot invalidations atomically. PRODUCT requires fresh interactive authentication for reentry. Delivery is after commit with leases and bounded retries; failed notifications cannot restore access. Repeated revocation creates no duplicate notice for already-closed sid. Back-channel delivery is at least once across crashes and uses a stable intent jti, never sub/person-wide logout.

POST https://id.test.globalbes.sg:9443/internal/control/v1/sessions/revoke

Called byPlatform ops AuthService certificate

Headers

X-BES-Operator

uuid

Optional acting person; permissions are intersected with the calling service.

Body

person_id*

uuid

login_scope*

enum

reason

string

sso_id

uuid

product_id

uuid

client_session_id

uuid

request_ref*

string

Stable caller reference; identical replay returns the first response; changed parameters conflict.

Request preview

POST /internal/control/v1/sessions/revoke

Response

Choose an API and send a request.

Caller tags:BOSSTenant adminAll productsMobile appMessagingControlAIAssistantPlatform opsLegacy productsCI release