Logout from operate or identity or tasklist doesn't redirect to login page instead it refresh current page!

Camunda 8 Topics Discussion & Questions
1

I am using c8run 8.8 alpha 8 and authentication is oidc
when trying to logout from operate or identity or tasklist, the page just refresh, and the user is not redirected to login page or any other landing/default page, I have to close the browser and open it again to be able to login with another user.

Please advise

2

Hi @devmsaleh,

Thank you for reporting this issue. What you’re experiencing is actually a known limitation in Camunda 8.8 alpha 8 when using OIDC authentication.

Current Behavior (Expected)

The logout functionality you’re experiencing is unfortunately expected behavior due to several documented limitations:

  1. Front channel single sign-out is not supported: When you log out from one component (Operate, Tasklist, or Identity), you are not automatically logged out from the other components. This is due to technical limitations with third-party content and how OIDC single sign-out works in browsers.

  2. Alpha release limitation: The Camunda 8.8 alpha release notes explicitly state that “Logout functionality is not fully supported across Orchestration cluster components.” This means logging out from one UI does not guarantee logout from the others.

Why This Happens

  • Session management and logout are not fully synchronized across Camunda components
  • Even after attempting to log out, you may be automatically logged back in due to existing OIDC sessions
  • Changes to authorizations or roles only take effect after a full logout and login cycle
  • Users must log out from each component individually to fully end their session

Current Workarounds

Unfortunately, there are limited workarounds for this issue:

  • You would need to manually log out from each application (Operate, Tasklist, Identity) individually
  • Clear all browser data/sessions related to your OIDC provider
  • This limitation affects the overall user experience in multi-component scenarios

Next Steps

This is a known product limitation that Camunda is aware of and plans to address in future releases. Since you’re using an alpha version, this behavior is expected to be improved in subsequent releases.

References:

Is there anything specific about your OIDC setup or use case that I can help you work around in the meantime?

3

Hi @devmsaleh
I’m facing this problem, I’m using Camunda 8.9.5, how did you solve it?