<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Databricks Apps (Streamlit) - How to Implement Proper Logout Functionality? in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/databricks-apps-streamlit-how-to-implement-proper-logout/m-p/164311#M55249</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;At the moment this is not a supported feature, you may want to raise it as a feautre request via your account team.&lt;/P&gt;
&lt;P&gt;Having said that there are a few things you could try to get a near but not perfect experience. Here are some options for you to explore:&lt;/P&gt;
&lt;OL class="css-0"&gt;
&lt;LI&gt;Combine a soft logout (clear session state, block UI) with shortened token TTLs. This would involve creating a is logged_in_user state in your streamlit app and then setting it from the logout button. You could then have some kind of logged out page in your app. You could then try reducing the TTL of the token, however the docs for this are mostly around third party applications so I can't guarantee this will definitely work for the app. Docs for this are &lt;A href="https://learn.microsoft.com/en-us/azure/databricks/integrations/manage-oauth" target="_blank" rel="noopener"&gt;here&lt;/A&gt;. You would also need to be an account admin to the second part.&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;If your organisation uses Azure AD / Entra ID (or another IdP), you can configure Conditional Access policies with session lifetime limits or sign-in frequency requirements, in conjunction with the sign out workaround. This maybe the best way.&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;I hope this helps with some ideas.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;&lt;BR /&gt;Emma&lt;/P&gt;</description>
    <pubDate>Tue, 28 Jul 2026 16:30:28 GMT</pubDate>
    <dc:creator>emma_s</dc:creator>
    <dc:date>2026-07-28T16:30:28Z</dc:date>
    <item>
      <title>Databricks Apps (Streamlit) - How to Implement Proper Logout Functionality?</title>
      <link>https://community.databricks.com/t5/data-engineering/databricks-apps-streamlit-how-to-implement-proper-logout/m-p/163987#M55212</link>
      <description>&lt;P class=""&gt;We have built a Databricks App using Streamlit and are looking for a way to implement a proper logout functionality.&lt;/P&gt;&lt;P class=""&gt;Currently, we built&amp;nbsp;Logout&amp;nbsp;functionality where&amp;nbsp;we can clear the Streamlit session state and client-side cookies. However, the Databricks authentication session remains active, and reopening the app automatically signs the user back in without prompting for authentication.&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;At the moment, the only way the user is logged out is when the Databricks access token/session expires.&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;Is there a supported way to completely terminate the Databricks authentication session from within a Databricks App?&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Can we force users to re-authenticate after clicking Logout?&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Has anyone implemented a reliable logout mechanism for Streamlit-based Databricks Apps?&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN&gt;I would appreciate any guidance or best practices from the community.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 24 Jul 2026 07:34:56 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/databricks-apps-streamlit-how-to-implement-proper-logout/m-p/163987#M55212</guid>
      <dc:creator>maninegi05</dc:creator>
      <dc:date>2026-07-24T07:34:56Z</dc:date>
    </item>
    <item>
      <title>Re: Databricks Apps (Streamlit) - How to Implement Proper Logout Functionality?</title>
      <link>https://community.databricks.com/t5/data-engineering/databricks-apps-streamlit-how-to-implement-proper-logout/m-p/164311#M55249</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;At the moment this is not a supported feature, you may want to raise it as a feautre request via your account team.&lt;/P&gt;
&lt;P&gt;Having said that there are a few things you could try to get a near but not perfect experience. Here are some options for you to explore:&lt;/P&gt;
&lt;OL class="css-0"&gt;
&lt;LI&gt;Combine a soft logout (clear session state, block UI) with shortened token TTLs. This would involve creating a is logged_in_user state in your streamlit app and then setting it from the logout button. You could then have some kind of logged out page in your app. You could then try reducing the TTL of the token, however the docs for this are mostly around third party applications so I can't guarantee this will definitely work for the app. Docs for this are &lt;A href="https://learn.microsoft.com/en-us/azure/databricks/integrations/manage-oauth" target="_blank" rel="noopener"&gt;here&lt;/A&gt;. You would also need to be an account admin to the second part.&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;If your organisation uses Azure AD / Entra ID (or another IdP), you can configure Conditional Access policies with session lifetime limits or sign-in frequency requirements, in conjunction with the sign out workaround. This maybe the best way.&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;I hope this helps with some ideas.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;&lt;BR /&gt;Emma&lt;/P&gt;</description>
      <pubDate>Tue, 28 Jul 2026 16:30:28 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/databricks-apps-streamlit-how-to-implement-proper-logout/m-p/164311#M55249</guid>
      <dc:creator>emma_s</dc:creator>
      <dc:date>2026-07-28T16:30:28Z</dc:date>
    </item>
  </channel>
</rss>

