powerkus

Hi,

Device Based Auth is not feasible for our usecase. Imagine several central systems, all with different users and rights. Every system manages several workflows with the need to access passwords. The easiest solution (for us) would be, to leverage Kerberos SSO via the API, as the scripts are run in the user context, but not necessarily with powershell.

The current solution only works with powershell - and only with your ps module since it leverages dll files from the RDM client. If anyone does not wnat to use ps, but leverage the KRB Auth with any other means, there is currently no way to do so.

If possible, the SSO feature from the Web UI would be nice to have in the API - without ps module.

You are correct. Thanks!

Hi

we noticed some misleading values for Last Changed By and

Created By on entries.

If a user starts RDM client, the value will always be the current

logged on user from the Windows system, no matter what user actually will be

used for making changes.

Example:

User A is logged on to a workstation, but uses another user (eq A_Admin) for

the tasks he wants to do in RDM.

The Value in the logs will always be User A, which is

misleading because this user does not have the rights to perform these actions.

It should be logged correctly, that the changes were made by

A_Admin.

This problem does not occur if the user works via browser. However, there could be more than the CreatedBY and CChangedBy values which are misleading.