<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Topics tagged with logout]]></title><description><![CDATA[A list of topics that have been tagged with logout]]></description><link>https://fusionauth.io/community/forum/tags/logout</link><generator>RSS for Node</generator><lastBuildDate>Sat, 14 Mar 2026 13:00:40 GMT</lastBuildDate><atom:link href="https://fusionauth.io/community/forum/tags/logout.rss" rel="self" type="application/rss+xml"/><pubDate>Invalid Date</pubDate><ttl>60</ttl><item><title><![CDATA[Logout with multiple subdomains]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="https://fusionauth.io/community/forum/uid/2507">@mark-robustelli</a> said in <a href="/community/forum/post/8049">Logout with multiple subdomains</a>:</p>
<blockquote>
<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="https://fusionauth.io/community/forum/uid/3540">@ext_figuvini</a> after reading your post again, I think I read it differently.  The way the SSO logout works is that on logout, FusionAuth calls all the logout urls for each applications. It would seem that you are correct in that creating an application for each subdomain makes sense and would work. (You can create applications through the API so you should be able to automate this.) Can you try this for a few domains and confirm it works?</p>
</blockquote>
<p dir="auto">Your point is correct. Creating a separate application for each subdomain is a reasonable and correct solution.<br />
When a user logs out of the SSO system, FusionAuth will call the logout URLs defined in each configured application in turn. This allows each application to clean up its own session. Pretty good solution</p>
]]></description><link>https://fusionauth.io/community/forum/topic/2929/logout-with-multiple-subdomains</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/2929/logout-with-multiple-subdomains</guid><dc:creator><![CDATA[blanfordkerry]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Identity provider logout]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="https://fusionauth.io/community/forum/uid/1212">@quent</a> I understand your position, and we appreciate the feedback.</p>
<p dir="auto">Can you please create a github issue linking to this forum post and with as much detail as you can provide (including, perhaps, sample logout urls provided by IdPs you are interested in)?</p>
<p dir="auto"><a href="https://github.com/fusionauth/fusionauth-issues/issues" rel="nofollow ugc">https://github.com/fusionauth/fusionauth-issues/issues</a></p>
]]></description><link>https://fusionauth.io/community/forum/topic/2271/identity-provider-logout</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/2271/identity-provider-logout</guid><dc:creator><![CDATA[dan]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Apple Sign in Provider , Logout]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="https://fusionauth.io/community/forum/uid/1298">@syed-muneeb</a></p>
<p dir="auto">Can you provide a bit more context about what you are trying to accomplish, the errors you are seeing, and other procedural steps?</p>
<p dir="auto">This may enable us to better assist.</p>
<p dir="auto">Thanks,<br />
Josh<br />
FusionAuth</p>
]]></description><link>https://fusionauth.io/community/forum/topic/1439/apple-sign-in-provider-logout</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/1439/apple-sign-in-provider-logout</guid><dc:creator><![CDATA[joshua]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Clarification on OAuth&#x2F;OIDC logout endpoint]]></title><description><![CDATA[<p dir="auto">Yea, that flexibility would be ideal IMO, although the registeredLogoutURLs should be workable for us at this point.  FWIW that is actually the behavior I assumed before digging into the docs.  I'll definitely add the issue to GitHub, as I think it's probably part of the path to getting OIDC Certification which appears to already have an issue.</p>
<p dir="auto">Thanks!</p>
]]></description><link>https://fusionauth.io/community/forum/topic/462/clarification-on-oauth-oidc-logout-endpoint</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/462/clarification-on-oauth-oidc-logout-endpoint</guid><dc:creator><![CDATA[Moonshine]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[logout questions]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="https://fusionauth.io/community/forum/uid/20">@dan</a> said in <a href="/community/forum/post/748">logout questions</a>:</p>
<blockquote>
<p dir="auto">'ve got a question about logout.<br />
When logging in using the /oauth2/token route with the auth <a href="https://wordle2.io" rel="nofollow ugc">wordle</a> code grant, it seems the /api/logout route does not revoke the refresh token.<br />
Is intended? Is the best way to log out in this case is with the /ouath2/logout route? How does that know which user to log out? there's no user id or refresh token property in the body.</p>
</blockquote>
<p dir="auto">Regarding user identification during logout, the OAuth 2.0 specification doesn't define a standard logout endpoint. Logout processes are often application-specific, and the mechanism to identify the user being logged out might depend on the authentication framework or technology being used.</p>
]]></description><link>https://fusionauth.io/community/forum/topic/270/logout-questions</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/270/logout-questions</guid><dc:creator><![CDATA[bekeanloinse]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Is there a way to have a user who logs out of an application go back to wherever they started from at login?]]></title><description><![CDATA[<p dir="auto">You can use the post_logout_redirect_uri query parameter on the logout endpoint to configure where a user ends up after  logout.</p>
<p dir="auto">More here: <a href="https://fusionauth.io/docs/v1/tech/oauth/endpoints" rel="nofollow ugc">https://fusionauth.io/docs/v1/tech/oauth/endpoints</a></p>
]]></description><link>https://fusionauth.io/community/forum/topic/35/is-there-a-way-to-have-a-user-who-logs-out-of-an-application-go-back-to-wherever-they-started-from-at-login</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/35/is-there-a-way-to-have-a-user-who-logs-out-of-an-application-go-back-to-wherever-they-started-from-at-login</guid><dc:creator><![CDATA[dan]]></dc:creator><pubDate>Invalid Date</pubDate></item></channel></rss>