<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D50Z00008G7VZ8SANOkta Classic EngineOkta Integration NetworkAnswered2024-04-16T12:57:35.000Z2018-07-26T22:51:44.000Z2019-02-11T07:05:44.000Z
  • Costel Curca

    Hi, Assuming that you have the application integrated with Okta, you can assign it only to a certain group or user for access.You can then gradually add more groups or users.

    Thank you,

  • a8nkl (a8nkl)

    Hi Costel,

     

    Yes you can do that, but once you enable SAML (e.g. Zoom), everyone who uses it will be redirected to Okta Login even if the app is not assigned to them.
  • Fred (Customer)

    Hi Nicole,

     

    This is a bit late I suppose but perhaps it could be of help to others.

     

    We found that for Zoom, unless you checked the security options to force all users of your domains to use SSO, they can still use their username and password to log in even though you have enabled SSO. Only once you have selected [Force users to sign in with SSO if their e-mail address belongs to one of the selected domains] under the Security settings of your Zoom tenant would all users need to sign in using SSO.

     

    This only applies to Zoom. As you mentioned, usually once you enable SAML for an app, all users are redirected to Okta for authentication. It's best to check with the application you're turning on SSO for to see how they handle SP-initiated SSO for the user base i.e. all in or you can get a choice.

     

    HTH.

    Expand Post
This question is closed.
Loading
Is there a way to do a phased rollout for SAML apps?