# Is it possible to do force logout without id\_token\_hint

**URL:** <https://devforum.okta.com/t/is-it-possible-to-do-force-logout-without-id-token-hint/20521>\
**Category:** OAuth/OIDC\
**Created:** [May 4, 2022, 5:16pm UTC](https://devforum.okta.com/t/is-it-possible-to-do-force-logout-without-id-token-hint/20521 "2022-05-04T17:16:34Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![erik](https://avatars.discourse-cdn.com/v4/letter/e/b5ac83/32.png) [@erik](https://devforum.okta.com/u/erik)\
**Post date:** [May 4, 2022, 11:30pm UTC](https://devforum.okta.com/t/is-it-possible-to-do-force-logout-without-id-token-hint/20521/2 "2022-05-04T23:30:28Z")

</div>

Hello,  
The correct way to logout of an OIDC application in Okta is to use the [/logout endpoint](https://developer.okta.com/docs/reference/api/oidc/#logout) of the authorization server the application used to /authorize into. This does require the id\_token in order to know the OIDC client that was used.

If you are mostly concerned with removing the Okta session cookie stored in the browser, then you _could_ use the same logout endpoint as when a user logs out of the Okta dashboard.

`https://{domain}.okta.com/login/signout?fromURI=http://localhost:3001`

The **fromURI** (a non supported parameter) will allow you to redirect the browser to any endpoint you have setup in the trusted origins with redirect capabilities.

_At anytime the fromURI parameter may stop working, and is not an officially supported parameter. Your application should be setup in a way so that is can correctly call the [authorization servers /logout endpoint](https://developer.okta.com/docs/reference/api/oidc/#logout) with the id\_token._

---

_[View the full topic](https://devforum.okta.com/t/is-it-possible-to-do-force-logout-without-id-token-hint/20521)._