RDM Hashicorp Secret Path wrong

Implemented

RDM Hashicorp Secret Path wrong

avatar

Hi,

we experience a strange issue with the Hashicorp Vault integration in RDM.

Our secret-engine (KV-v2) is mapped to the path "so/secret" and therefore, we define as Hashicorp Vault entry in RDM the following values:

The secret path is set to "so/secret/test/0000000/ad (test.local)/Administrator/Administrator"

If I try to use this entry I get the error message "permission denied". While analysing the access logs for Hashicorp Vault I can clearly see, that RDM tries to access the path "so/data/secret/test/0000000/ad (test.local)/Administrator/Administrator". In our case, this is wrong because the "data" keyword should be placed after the secret engine "so/secret" and not in between. The correct path should look like "so/secret/data/test/0000000/ad (test.local)/Administrator/Administrator".

Have you an idea how to fix this issue?

All Comments (16)

avatar

Hello,

I have created an internal ticket to address your case.

In the meantime, would you be open to scheduling a remote session to further discuss the issue?

Best regards,

Carl Marien

avatar

Hi Carl,

thank you!

Sure - what information (or access to which services/servers/applications) do you need for it?

avatar

Hello,

We typically use remote sessions for troubleshooting; however, our developers have identified the root cause of the issue you are experiencing. They are actively working on a solution to resolve it.

We will keep you updated as we make progress.

Best regards,

Carl Marien

avatar

Great, thank you for your effort!

avatar

Looking forward to test it after the update has been released.

I'll keep you posted.

avatar

Hello,

I apologize for the inconvenience. Our developers are still working on the issue you reported. I'll keep you updated on our progress.

Best regards,

Carl Marien

avatar

Hello kschweiger,

A quick adjustment there was a miscommunication on our end. A fix should not be implemented in RDM 2023.3, but we plan on tackling that issue once this major release is out.

We will keep you updated on any new developments on that matter.

Best regards,

James Lafleur