Cross Vault Credential Usage

Thank you for the suggestion.

With our current version (v2020.3) the vault architecture does not support this type of feature. We are changing the internal architecture of vaults with the soon to be released version 2021.1. In the future this type of feature could be possible. I will add your suggestion to our list so that we can investigate its feasibility.

Best regards,

+1 for this feature request. Would help us a lot.

Hi,

is there any update on this feature request or probably a roadmap/timeline for it?

Best regards

Hi all,

I’m currently working on this feature and have just over three weeks to deliver it for inclusion in the 2025.1 release. At this time, it’s still too soon to say for certain whether I’ll be able to complete everything needed on time.

Reflecting on my earlier comment, it’s hard to believe this feature was first requested four years ago—how time flies! With the release of 2024.3, we made significant progress, including enabling background vault synchronization, which was a critical stepping stone toward cross-vault credential linking.

Currently, I’m focused on rewriting and validating the variable-resolving code. This is essential for allowing RDM to isolate each vault so that variables can be resolved independently, without cross-vault contamination. I’ll also need to apply the same changes across each subsystem in RDM (permissions, inheritance, etc.).

I’ll provide another update once the feature is released.

Best regards,

Hi all,

I’m currently working on this feature and have just over three weeks to deliver it for inclusion in the 2025.1 release. At this time, it’s still too soon to say for certain whether I’ll be able to complete everything needed on time.

Reflecting on my earlier comment, it’s hard to believe this feature was first requested four years ago—how time flies! With the release of 2024.3, we made significant progress, including enabling background vault synchronization, which was a critical stepping stone toward cross-vault credential linking.

Currently, I’m focused on rewriting and validating the variable-resolving code. This is essential for allowing RDM to isolate each vault so that variables can be resolved independently, without cross-vault contamination. I’ll also need to apply the same changes across each subsystem in RDM (permissions, inheritance, etc.).

I’ll provide another update once the feature is released.

Best regards,

Hi Stéfane,

I was searching for cross vault linking in my case cross vault credential linking, then came accross this post, I see you were working on something for a 2025.1.x release, did it happen?? If so exaclty what was it, I see you mention variables but will your addition / change work for my scenario?? Granted I mainly use my personal vault or now PAM vaults for most credentials, but as you can tell I've come accross the need to use Credential entries from another vault but have been hitting a road block on how to proceed, I initially looked for an entry that could link cross vaults but couldnt find anything, then I started to look if Syncronizers could work, which then led me to consider just scripting this (This is similar to another problem ive not succeeded with which is propergation scripts for PAM vault creds). Anyway, would what your working on work for my scenario, has it released yet (soz yet to search through rls notes)

Hi all,

I’m currently working on this feature and have just over three weeks to deliver it for inclusion in the 2025.1 release. At this time, it’s still too soon to say for certain whether I’ll be able to complete everything needed on time.

Reflecting on my earlier comment, it’s hard to believe this feature was first requested four years ago—how time flies! With the release of 2024.3, we made significant progress, including enabling background vault synchronization, which was a critical stepping stone toward cross-vault credential linking.

Currently, I’m focused on rewriting and validating the variable-resolving code. This is essential for allowing RDM to isolate each vault so that variables can be resolved independently, without cross-vault contamination. I’ll also need to apply the same changes across each subsystem in RDM (permissions, inheritance, etc.).

I’ll provide another update once the feature is released.

Best regards,

Hi Stéfane,

I was searching for cross vault linking in my case cross vault credential linking, then came accross this post, I see you were working on something for a 2025.1.x release, did it happen?? If so exaclty what was it, I see you mention variables but will your addition / change work for my scenario?? Granted I mainly use my personal vault or now PAM vaults for most credentials, but as you can tell I've come accross the need to use Credential entries from another vault but have been hitting a road block on how to proceed, I initially looked for an entry that could link cross vaults but couldnt find anything, then I started to look if Syncronizers could work, which then led me to consider just scripting this (This is similar to another problem ive not succeeded with which is propergation scripts for PAM vault creds). Anyway, would what your working on work for my scenario, has it released yet (soz yet to search through rls notes)

Scrap my previous I've just answered my own question DOH!!

This entry did the job...

Hi JK,

The feature didn't make the cut for the 2025.1 release. We still had too much internal code rewriting to do before being able to support cross-vault credential linking. The good news is it will be included in 2025.2. The code isn't complete, but we are far enough into the implementation to confirm it will be included.

Using a Hub credential is a smart way to circumvent the current limitation. It's somewhat cumbersome to configure but does the job. Cross-vault (or external vault) credential linking will be much easier.

Feature sneak peek; here is a video of the configuration form.

Best regards,

yeah that dph cred entry does the job, having my account settings set to the right entra user used for dph sso seems to prevent the extra steps to access the vaults, I like your form but would it look cleaner to have linked (vault) as it is now with the popup selector window with the tree view that defaults the current vault again, then add a vault selector drop down accross the top alongside the existing form fields where you see the vault search field with a 'name', 'tag' etc drop down field to its right, add a vault drop down there somewhere?? That way it should look much cleaner and users still have the expected linked (vault) which going by assumptions seemed like it should be doing what your changing now linking creds from vaults......

hi Stéfane,

Question, I tried to create another linked credential entry today using my workaround as mentioned above, but this time when I tried to pick a credential from my PAM Vault it didn't populate with entries like it had been, I also notice that the icon for the PAM Vault is a generic yellow folder icon when before it's a circular fav icons that you normally see for Vault names. Now nothing whatso ever has changed apart from regular updates, now I can't be sure If this is the first attempt at this workaround at my current version 2025.1.33.0 or whether it was 2025.1.33.0 when it was working or whether it worked in 2025.1.32.0 but isn't now??? I'm about to try in 2025.1.34.0, if there's any change Ill update this post but I'm not holding my breath as it may be an update with DPH bus that's patched my workaround?

How far off is your addition?

Thanks

Hi JK,

The feature didn't make the cut for the 2025.1 release. We still had too much internal code rewriting to do before being able to support cross-vault credential linking. The good news is it will be included in 2025.2. The code isn't complete, but we are far enough into the implementation to confirm it will be included.

Using a Hub credential is a smart way to circumvent the current limitation. It's somewhat cumbersome to configure but does the job. Cross-vault (or external vault) credential linking will be much easier.

Feature sneak peek; here is a video of the configuration form.

Best regards,

Stefane,
This is great, i believe this is what I've been waiting for. Thank you for the video!
Any idea on a timeline for 2025.2 release?

2025.2 will be released next week. You can try the beta in the meantime.