V13.5.6 - credential shortcut bug

Hello,

Thank you for posting this.

I will have a look with our engineering team.


Best regards,

Hello,

This is a known behavior which can't be fixed for now.

Since RDM currently saves the selected credential repository by "ID" instead of by "path + name", it is impossible to show the path of the "shortcut". It will always show the "original" credential entry.

This shouldn't cause any issues since you can't edit the properties of "B\1" without it being changed on "A\1" (they are one and the same).

The only case where it will display the shortcut's path is if your user doesn't have view permissions to the folder "A". Your selected credential repository will then be shown as "B\1".

We sincerely apologize for any confusion or inconvenience this may cause.

Regards,

Hi Michaël,

Thank you for your update! This is really bad news and will make our 2k entry repo a visual mess.

We've spent the last few days creating credentials shortcuts which right now have absolutely no visual coherence with credentials they belong to.

Do you have a fix for this on your roadmap?

Regards,

Rafael

Hello,

Since this is an important issue for you guys, we will do our best to come up with a workaround as soon as possible.

I will keep you updated on the progress and let you know if we can fix it or not after a more in depth investigation.

Regards,

Hi Michaël,

That's great news!!! Thank you so much for your effort!

Rafael

Hello Rafael,

We have changed the behavior for the credential selection so that it selects shortcuts.

However, this will only work if the shortcut is in the same folder as the entry which is getting it's properties browsed. The behavior will be the same as before if the selected credential shortcut isn't in the same folder as the entry using it.

Those changes will be available starting from the next beta of RDM. Hopefully this will fix your issues.

Regards,

Hello Michaël

That's such great news! Thank you so much.

As soon as we get the next beta, we'll try it out and let you know how it's working

Once again many thanks

Rafael

Hi,
we are running on server version 5.1.1.0 and client 13.6.7.0 and this is still a problem.
What is the expectation for the fix?
Thanks

Ricardo Marques

Hello Ricardo,

The change we made is as follows :

If this doesn't help, we can keep looking for other possibilities. However, there is no perfect solution as a shortcut is not an entry of it's own. It is simply the original entry shown in multiple locations.


Regards,

Hi Michael,
please consider the following folder structure:


Folder A(root folder)
Folder B(child)
Folder C(Child)

If we create a credential shortcut in Folder B and then copy over to Folder C will the latter show C in properties/general/folder?

Currently it will show B in properties/general/folder

What we would like, would be to show C.

Best Regards
Ricardo Marques

Hello Ricardo,

The only way we could achieve what you want with how the shortcuts are working is to save the path of the credential shortcut which you have selected.

For example, if you have the following choices :

"CredentialFolder\B\CredentialShortcut"
"CredentialFolder\C\CredentialShortcut"

If you select the shortcut in the folder "C", then we would save the path "CredentialFolder\C\CredentialShortcut". When you open your properties, we would then be able to show the same path again.

However, the big issue with this is how inconsistent it is. If someone decides to change the name of the folder "CredentialFolder", the folder "C" or of the credential itself, then the path will be faulty and the behavior will go back to how it is currently working.

Please do let me know if you would like this change to be applied even if it would break every time someone changes the name of the folders above the credential shortcut or of the credential's name itself.

Regards,

Hi Michael,
thank you very much for the suggestion.
Yes please apply this change, it will help us.

Best Regards
Ricardo Marques

Hello Ricardo,

This feature will be available starting from the beta of RDM 14.

Regards,