Connecting RDM to Azure Key Vault

Hello,

Thank you for contacting us on that matter!

Unfortunately, we do not have documentation for specific entry types since they are bound to change often as new features/improvements are made to them. That being said, could you please provide us more details about the issue you are experiencing?

Also, which version of RDM and what type of Data Source you are currently using?

Best regards,

We are currently running the latest version of RDM and use Azure SQL as well as regular SQL DB's. I guess my issue is maybe I'm not entering the right data to connect because I get an error - there was an error fetching the secret list. I'm guessing that means it's not connecting properly.

If could assist - I feel like I'm missing something really stupid here.

For URL - I am putting the URL of our Azure Key Vault
For Tenant ID - I am putting the "Directory ID" of our Key Vault or our Tenant ID of our Azure AD - they are the same

I checked the "Use My Account Settings" box because I filled in that Azure AD info in My Account Settings.
In there I put Client ID/Client Secret of the Azure App I registered for the key vault

Then I put my user name and hit the ... to put my secret and that's where I get the error - error fetching the secret list.

Any help would be greatly appreciated!

Hello,

Thank you for your swift reply!
The profiler logs might be able to provide us more details on this issue. For this reason, could you please do the following:

1- Go under Help -> Profiler -> Debug Only -> Set the "Debug level" at 1
2- Move the Profiler window to another screen.
3- Go in the properties of your Azure Key Vault entry and click on the ellipsis button (...)
4- While RDM establishes the connection, logs should be generated in the profiler window. If it is the case, please send them to me via private message.
5- Set the "debug level" back to 0 after performing this test.

Best regards,

Hello,

Thank you for sending me these logs, I will provide them to our Engineering Department and see what can be done on that matter.

Best regards,

Awesome thanks for your help!

Are there any updates on this? I haven't heard back from anyone yet

Hello,

You are more than welcome!

A ticket has been opened with our Engineering Department to analyze your case. Since the engineer in charge of this feature will be back next week, we should be able to provide an update then.

Best regards,

Hello Bailey,

Has your App Registration been created recently ? Sometimes their token can expire, so the client secret becomes invalid.

Either way, you could try creating a new secret and use that new one in RDM to make sure you're not using an expired one.

Looking forward to your results,

Regards

I literally created the app registration just for this...That's why I feel like I must be doing something stupid.

I tried making a new Secret but it's failing with the same error. Both my "old" and new secret expire in 2022. Am I just putting in the wrong information or something?

URL = Our Vault URL "x.vault.azure.net"
Tenant ID: Our Tenant ID for Azure
Client ID: App Registration's Client ID
Secret: Secret ID in the App Registration
UserName: my azure login
Secret - I'm clicking the "..." when I get the error. "Error fetching the secret list"

It also fails if I check the "use my account settings"

I just got access to a working setup, and I think I may have found the reason you're having issues.

For the client secret, you have to enter the client secret value, not the client secret ID.

Hopefully this resolves your problem.

Regards

Even using the secret value gives me the same error. Ugh, sorry.

In that case, would you mind doing the procedure James posted earlier and send me the logs via private message ?

I want to confirm if the issue is still related to the client secret or if there's something else.

Thanks!