'Allow reveal credentials (everybody)' not showing on new credentials entry?

Hello,

This checkbox has been removed in the most recent versions of RDM. In order to avoid issues with already created entries, this change is only present when you create a new credential (username/password) entry.

This setting has been moved under Security - Permissions - View Password, in the Properties of your entry


Best regards,

Thanks James,

For that same entry if I go to the Permissions I have nothing showing there at all. I've checked this on 2 different machines.

Hello,

Do you wish to allow your user to see all your passwords or only a select few?

Best regards,

No, we do not wish to give the users access to all credentials. We had been using the 'Allow reveal credentials (everybody)' checkbox to allow the users to access the credentials only on certain entries where we find it's absolutely necessary.

Hello,

I had a discussion with our engineering department and this issue is currently under investigation.
I will notify you as soon as I have any update on that matter .

Best regards,

Thanks James, we're looking forward to the fix for our predicament! :)

Hello Jamieson,

The reason you don't have access to the permission settings is probably because you are using DODB. We have changed the behavior of the "Allow reveal credentials (everybody)" checkbox and made it visible once again for DODB users.

This change will be available starting from the next beta of RDM and will hopefully fix your predicament.

Regards,

Thanks Michaël,

It's a valuable feature to us to be able to allow users to copy/paste credentials when necessary. For example, when a user must connect to a secondary RDP connection after the first. We're also finding that setting up LogMeIn connections can be hit or miss. Sometimes they work, sometimes they fail to login the final step and the user needs to enter network credentials. Some VPN's are also very ... challenging... such as the newer FortiClient console which no longer has CLI support... and the current Cisco AnyConnect CLI issue caused by recent Windows Updates. We support a large number of clients, each with their own remote access solution, so we're dealing with a large array of connection types. It's a hot mess to say the least.

Thank you for the update. Any idea when we might expect the next release for this fix?

Jamie

Hello Jamie,

If nothing goes wrong we should have the fix released some time next week at the latest.

Regards,