SAML authentication preventing me to enroll devices and configuring CyberArk mobile app.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

SAML authentication preventing me to enroll devices and configuring CyberArk mobile app.

L1 Bithead

Hi community,

 

We have deployed CyberArk Cloud Shared services in my client's systems and we cyberark uses SAML automatically as authentication method when a @domain email account is introduced in the login portal. The point is that SAML does not allow the login from outside the corporative network so it is preventing all users to configure the CyberArk Mobile App for using it as 2FA. 

 

Any clue about how to disable SAML or at least put it as optional? SAML is also presenting problems when launching sessions from PSMP module.

1 REPLY 1

L6 Presenter

Shared Services has some unique requirements around MFA to enable full functionality; for example, native SSH connections through the PSMP and native RDP connections through a connection manager are only supported when CyberArk Identity MFA profiles are in use, meaning an external IdP integration (SAML) is not a possible MFA method for the native connections. Bottom line - if the customer is using their own SAML solution, then they must go through the web portal to access accounts (no native connections).

 

There are some workarounds to this limitation. The PSMClient on the Marketplace supports external IdP for native RDP connections, and MFA caching for the PSMP covers native SSH.

 

My recommendation to customers is to NOT use an external IdP integration if at all possible, and to instead use the native MFA built into the product to enable full functionality.

 

In Shared Services, the customer basically has two options when it comes to user authentication: First is the user directory we are looking up the user from, and second is the MFA method applying to that user. An external IdP can be used as one or both pieces of this equation (so it can provide MFA for AD users, for example, or it can be both the directory and MFA source combined).

 

SAML can be disabled in shared services be deleting or disabling the external IdP integration: https://docs.cyberark.com/Product-Doc/OnlineHelp/Idaptive/Latest/en/Content/CoreServices/UsersRoles/PartnerAdd.htm

 

Once SAML is disabled you will want to ensure there is an MFA method set up for user authentication that works. The preferred method to do this is again the native MFA built into Identity. You can find details on setting up the MFA profiles here: https://docs.cyberark.com/Product-Doc/OnlineHelp/Idaptive/Latest/en/Content/CoreServices/Authenticate/ConfigAllCond.htm?tocpath=Set%20up%20CyberArk%20Identity%7C_____2

  • 345 Views
  • 1 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!