louissanderson

Hi Jonathan,

Just following up on the above. Any news?

BR

Louis

Hi Jonathan,

It's been a while :)

Don't suppose you know any more since the last update?

Cheers,

Louis

Hi Jonathan,

Just wondering if you have made any in-roads or if it is still causing problems.

Cheers,

Louis

user (userpass) had been created via UI but as you mentioned CLI I decided to give that a try just now. ("vault write auth/userpass/users/<user> policies=las-testing password=<password>")

I got the same result as users created via UI.

Louis

Thanks Samuel,

Hi Jonathan,

We have tried user/pass and token. Both with the same outcome.

Cheers,

Louis

update, I just noticed that there is an update available for RDM.

Version is now: 2024.1.19.0 64-bit

No change in the vault permissions working unfortunately.

Hi Samuel,

RDM is currently running version 2024.1.17.0 64-bit

Data Source is MS SQL

This is a completely new thing that we have not used before in the past.

Louis

Good afternoon all,

I am trying to implement some sort of permissions so that a single HCP vault credential entry in RDM can only access certain Secret Engines in HashiCorp Vault.

I have the policies set as I think they should and in the UI, the account used can only see the required vaults as per the policy set in HCP UI. However, In RDM, It lists all the engines and not just the ones I want.

Could anyone provide some insight into what I am doing wrong or if this is a limitation of either RDM/HashiCorp.

Cheers,

Louis