mnr

We have a lot of Azure Service Principals registered in vaults.

As these service principals are used in integrations where only the App Id and secret are noted in code, it is not always clear, under what name to find the entry in the vault.

It would seem that it is not possible to set 'Client ID' as a search filter, but maybe I just cannot find it :)

An alternative is to include the Client Id in the entry name as well as the friendly display name, but that requires changes to a lot of entries.

Is it possible to set this field as a search filter or are there any other solutions that I cannot seem to find?

Hi all,

We are hoping there is a way to get access to the RDM REST API in the current users context and not with a API Key/Secret as this has read/write (depending on role?) permission to all the entries in the vault(s).

It seems the documentation about this is a bit lacking

(https://docs.devolutions.net/server/web-interface/utilities/api-documentation)

(https://{ACTUAL-RDM-URL}/api-documentation)

Is it possible to get any of the following to work - and if so how do we do that?

1. Get an access token from our IdP (Entra) by OAuth 2.0 (user delegation/auth code/interactive login...?) and use this in a https request header to the API

2. Get an access token from using "Authorisation: Basic user pass" in a https request header to the API login endpoint

3. Get an access token from using the windows login current user credentials somehow (We have also setup SSO with AD and Entra in Devolutions Server)

4. Another way to query the API in a user context?

Thanks in advance :)