Offline caching not working when accessing DVLS via Azure App Proxy

Backlog

Offline caching not working when accessing DVLS via Azure App Proxy

avatar

Hello,

Using RDM 2025.3.30 and DVLS 2025.3.15. When connecting via Azure App Proxy, entries are sporadically appearing as read only, cannot be launched, and sometimes not visible. For example:

  • when right mouse clicking on an entry the 'open session' and 'properties' options are greyed out, which prevents launching or editing
  • sometimes when switching between vaults, all the entries disappear, and a message is displayed that there is no access (going offline and back online usually resolves it)


If caching is disabled for the data source, then these limitations are removed, however as soon as caching is reenabled (either file or memory), the behavior returns.

Please let me know if you would like any additional info.

Thanks
Joe







74dad01a-3672-4402-a767-f4519322cf9c.png

20687e4e-f9fa-412d-a638-56372d112c47.png

fddad769-3887-4c03-870a-9452e5668e42.png

e934dbda-e646-4ed1-94aa-9db0f133b32b.png

All Comments (4)

avatar

Hello Joe,
Based on the behaviour you described (entries intermittently becoming read-only, actions greyed out, and vaults appearing empty until you toggle offline/online), this strongly suggests RDM is intermittently falling back into an offline/degraded state and then relying on the local cache. When the effective offline access resolves to Read-only (or the cache for a vault is not yet built), you can see exactly the symptoms you are reporting.
To narrow this down, could you please provide the following at the moment the issue occurs (when “Open session” / “Properties” are greyed out or when a vault shows “no access”)?

  1. RDM state
  • Does the “Go offline” indicator in RDM’s status bar switch to Offline (orange) when this happens?
  1. Effective offline configuration (single screenshot or copy/paste is fine)
  • In RDM: File – My data source information (this shows “Allow offline mode”, auto refresh state, and effective rights)
  1. Offline mode settings (confirm the effective values)
  • In RDM (DVLS data source): Data source properties > Edit data source > Advanced tab > Caching mode (Disabled / In-memory / File)
  • In RDM: Administration – System Settings – Cache/offline > Offline mode (Cache-only / Read-only / Read/write)
  • In DVLS: Administration – System settings > Users > “RDM offline mode.”
  • In DVLS: Vault settings > Security settings > “Allow offline” is enabled (and confirm the vault security level is not set to High)

In the meantime, you can also try these quick actions:

  • Press Ctrl+F5 to force a refresh of the local cache when entries are missing.
  • If the cache seems stuck/out-of-sync, delete the offline cache file (offline.db) for that data source and let it rebuild (close RDM first).

Documentation (for reference)

Best regards,

Patrick Ouimet

avatar

Hi Patrick,

Thanks for assisting with this one.

Yes it does appear RDM is reverting to offline mode behavior, even though it is reporting that the data source is online. The issue occurs when caching set to 'memory' which I think rules out file corruption. Auto refresh not enabled.

Pressing CRTL+F5 does make the entries come back after getting to state where RDM says 'no entries accessible', but RDM locks up for minutes (or indefinitely) while it is (re)populating local cache.

RDM works fine via Azure App proxy if caching is disabled. When RDM has direct connection to DVLS, caching works fine, which I think implies the server-side settings are ok.

Appears as though caching is broken when using Azure App Proxy, in the sense that it runs modally and causes app to be unresponsive, along with retrieval buffering times outs resulting in a pseudo offline mode and/or corrupted cache.

Are you able to reproduce any of this behavior on your end?

Joe

45541489-56e1-4e42-b1d7-cb25f5928832.png

avatar

Hello Joe,

Thank you for this feedback.

I can't reproduce this issue.
I will open a ticket and send you a link to schedule a session and have a look.

Best regards,

Patrick Ouimet

avatar

Hi Patrick,

Have scheduled call for next week.

Can also confirm the same behavior exists with RDM 2026.1.10 connecting to DVLS 2025.3.15

Joe