PAM Permission sets not being saved

A fix for this issue has been implemented in version 2026.1.15.0
Implemented

PAM Permission sets not being saved

avatar

Hello,

Using DVLS 2025.3.15. After adding a new permission set in Administration\System Settings\PAM Vault Management, then clicking save (which displays a message saying saving was successful), then navigating to a PAM vault to apply the permission set, it is not listed. Navigating back to system settings, the recently added set is no longer present, as though it was never saved.

Please let me know if any additional information required.

Thanks
Joe

All Comments (8)

avatar

Hello,

Thank you for contacting us about this.

I have created a ticket regarding this issue and we will review it shortly.

Best regards,

Simon Leroux

avatar
Hello,

Using DVLS 2025.3.15. After adding a new permission set in Administration\System Settings\PAM Vault Management, then clicking save (which displays a message saying saving was successful), then navigating to a PAM vault to apply the permission set, it is not listed. Navigating back to system settings, the recently added set is no longer present, as though it was never saved.

Please let me know if any additional information required.

Thanks
Joe


@jm2
Hi Joe,
I’m writing to let you know that we were able to reproduce the issue, and a fix will be implemented shortly.
In the meantime, could you please confirm how you saved your changes when exiting the System Settings page? Did you use the save prompt upon exit, or did you click the floppy disk icon in the upper-right corner of the page?
If you did not use the floppy disk icon to save, please try doing so, as this should resolve the issue.
Best regards,
Sayed

avatar

Hi Sayed,

Thanks for assisting with this. I tried both approaches for saving, and neither worked.

Joe

avatar

Hi Sayed,

Any update on ETA of fix for this?

Thanks
Joe

avatar
Hi Sayed,

Any update on ETA of fix for this?

Thanks
Joe


@jm2
Hi Joe,

A Dev is currently working on a fix for the issue, i will keep you posted here when the fix is done.

Regards
Sayed

avatar

Hi Joe,

I’m pleased to inform you that this issue has been resolved in DVLS version 2026.1.15.0, which is scheduled for release next Tuesday.

Best regards,

avatar

That's great, thanks Sayed

avatar

Hello,

I am pleased to inform you that the issue has been resolved in the latest Devolutions server version (2026.1.15.0):
https://docs.devolutions.net/server/getting-started/installation/upgrade-server

We also recommend that you first perform the update in a staging/test environment:
https://docs.devolutions.net/server/kb/how-to-articles/create-server-staging-instance

We also offer free upgrade sessions, during which we will update your Devolutions Server instance together. If you are interested in this, please send an email to service@devolutions.net

Best regards,

Maxim Robert

A fix for this issue has been implemented in version 2026.1.15.0