Desktop client always asks to reconnect after OpenCloud server restart (OIDC tokens not reused?)

[Mayurifag]

I’m seeing consistent re-authentication behavior with OpenCloud Desktop after restarting the OpenCloud server, and I want to understand whether this is expected or a bug/misconfiguration.

Observed behavior

• OpenCloud Desktop works normally while the server is up.
• After restarting the OpenCloud server, the Desktop client prompts me to reconnect
• Nothing changes on the server side (same config, same user, same IdP).
• This happens every time the server restarts.

Expectation

I would expect the Desktop client to:

• Reuse stored credentials or refresh tokens
• Automatically recover the session after the server is back online
• Not require interactive login unless credentials actually changed or expired (I do not want them to expire actually or make it once a year idk)

Environment

I’m using this Ansible role to deploy OpenCloud (including Traefik integration), shared here for reference in case something relevant stands out:

https://github.com/Mayurifag/mayurifag.ru/blob/main/roles/opencloud/tasks/main.yml

Questions

1. Is OpenCloud Desktop expected to lose its authenticated session after a server restart?
2. Are refresh tokens or signing keys invalidated on restart by design?
3. Is there a known limitation with OIDC + Desktop + reverse proxies (Traefik)?
4. Are there specific persistence requirements (volumes, keys, secrets) that must survive restarts to allow token reuse?
5. Has anyone achieved seamless Desktop reconnection after server restarts?

[micbar]

Cool that you are using ansible to deploy opencloud..

I have not so much experience with the default built in IDP. I am using keycloak and that works perfectly.

Maybe the internal IDP doesn't handle the existing sessions during restart? @rhafer Do you know that?