Logout
When the customer logs out of your application, first clear your own session and tokens, then (optionally) redirect the browser to the INEX ID logout endpoint so they are signed out of INEX ID too.
GET
{issuer}/oauth/logout
GET {issuer}/oauth/logout with these parameters:
| Field | Required | Description |
|---|---|---|
| id_token_hint | Recommended | The id_token received at sign-in (it may be expired). Says which account to sign out and names your client. |
| post_logout_redirect_uri | No | Where to send the customer afterwards. Must be one of your client's registered addresses — otherwise it is ignored. |
| client_id | Conditional | Required for post_logout_redirect_uri when you do not send id_token_hint. |
| state | No | Returned unchanged on post_logout_redirect_uri. |
Behaviour
-
One INEX ID browser may hold several signed-in accounts. With
id_token_hintonly the account in the hint is signed out; without it, only the active account. - Logout does not revoke access/refresh tokens you already hold — delete them yourself.
-
Without a registered
post_logout_redirect_urithe customer stays on the INEX ID page.
Logout (302 redirect)
HTTP
GET https://id-staging.inex.ge/oauth/logout
?id_token_hint=eyJhbGciOiJSUzI1NiIsImtpZCI6Ii4uLiJ9...
&post_logout_redirect_uri=https%3A%2F%2Fshop.example.com%2Fauth%2Finex%2Fcallback
&state=AFTER_LOGOUT
Back to you
HTTP
GET https://shop.example.com/auth/inex/callback?state=AFTER_LOGOUT