Adoption of Delinea Platform authentication flow
Hi Jonathan,
>Thank you for the detailed request. Before we go further, I want to make sure I understand the problem. From what you describe, your Platform-native users get the Delinea Platform login page inside RDM. Is your main concern that you don't want that login page? Or do users sign in successfully, but RDM then fails to browse, search, or retrieve secrets?
That's right; RDM does not retrieve the session authentication token from our 100% finalized Delinea platform for this “native” regular platform user.
>If it's the login flow itself, that's expected. Users created directly in the Delinea Platform have to sign in through the Platform's own login page, which is where your identity provider and MFA are handled. Delinea doesn't let an application like RDM sign these users in with just a username and password, the way Secret Server allows for its own accounts.
That's right, authentication takes place via the platform's login page, but the bearer token couldn't be passed, and the RDM got stuck on the platform page and the login page itself, so no further RDM actions are working. It looks like the RDM can't handle native platform users.
> f you really need to avoid the login page, the only other option would be Delinea Platform service users. These are accounts that Delinea provides for integrations, and they can sign in without the embedded browser. RDM doesn't currently support that option, but it's something we could look at. Each user could have their own service user, saved in their RDM My Account Settings, so nobody shares an account and the Secret Server audit log still shows who did what.
We didn't want to bypass the login page; rather, we wanted to set up a functioning platform login and access to Secret Server secrets through the platform so that the platform would allow users to correctly retrieve the secrets from the platform (and the Secret Server contained within it) for normal RDM use. This is currently not working—despite the platform having been migrated to its final version and a Delinea platform user account having been 100% converted and recreated.
>Keep in mind that a service user isn't the person's own Platform account, though. Each person would need an extra account for your admins to create and maintain. Its permissions would need to be kept in sync with the person's own. It doesn't go through MFA or your identity provider's sign-in rules. And it has to be disabled separately when someone leaves.
In conclusion, we don't want to use service users; instead, real, 100% platform users should be able to log in and retrieve secrets from the platform via RDM, just as it previously worked natively with Secret Server users in conjunction with RDM.
Thank you, Jonathan, for your explanations. We’d be happy to work through this together in a short session using the latest RDM version and in our Delinea test tenant. Currently, we’re seeing an issue with the transfer of credentials from 100% Platform users to RDM and authentichation with Platform users.
Thank you & Best regards,
Thomas Balatka