Robert Laskus

Hi ,

i need to import a lot of entries from a CVS, the entries may be different ( RDP, SSH , Webpage etc) so i need a way to "identify" the entry/connection type

but i couldn't find a list of valid values for the "EntryType"

we have also some templates created for RDP of use "my Personal Credentials" , how could i use as a value

does anyone got an idea ?

Changed the my Priv Cred setting to SSO

I've been ask to provide my password .. but i'm missing the web window for the SAML login ... how does this work?

Which account is taken ?

i our case we may have different accounts for Secret Server and RDM SQL Database .. so i guess it might get mandatory to have this web login window

it would be at leased more transparent .. any idea who i can bring this back ?

Robert

Too bad :(

version 2023.3.20.0 was working with our On-Prem solution with SAML .. all we were looking for was working

but now i can see there was a "fix" at 2023.3.22.0 with the comment "Fixed Secret Server on-premise authenticating with web login instead of oauth"

i fear this will disable the SAML ability in our Env ... so this is no fix for me :(

i'll definitly stay on 2023.3.20.0 until you fix the fix again :)

robert

This sounds promising .. looking forward to the On-Prem function .. do you have any time estimations ?

Robert

to me this sounds quick and dirty , but if a login page of SecretServer would appear for all the SAML stuff and the API token would be used to gather all following info .. this would be good enough i guess

we're in the same boat, we've established our structure in RDM and would like to keep it. In the link I've attached it is mentioned that the SAML authentication should be supported from RDM version 2023.1 onward and we were kind of relying on this, but about nine months later after the release of 2023.1 there is still no sign of this implementation. I don't know of any other products which offer all the integrations like RDM, so at the moment we're thinking about starting with the AD integration of the users and move to SAML after RDM is able to. This is causing some major delays in our project but we don't see other ways atm.

Right , this is really disappointing .. my company is unfortunately not waiting for RDM to get this working : SecretServer is already switched to SAML (as well as many other services). So using RDM is not Impossible anymore, but we lost a lot of comfort and functionality. And the bigger the pain gets , the louder the discussion gets about replacing to a product which is able to handle this

sorry my fault .. my company is using Azure AD with SAML :(

so the described option is not solution for us

This is really bad news .. my company requires the MFA authentication

it is activated at SecretServer and we are not more able to access the stored password from RDM .. i bet a RDM replacement discussion will start soon

Would be too bad, as we all love your product :(

Robert

Hi , are there any news on this toppic ?

we facing the same issue

Regards Robert