![]() The Application ID has to be the same as the text string that is specified as the target in the code of the mobile application written using the mobile SDK. CyberArk Identity uses the Application ID to provide single sign-on to mobile applications. For example, if you login to Zoom using, enter acme.Ĭonfigure this field if you are deploying a mobile application that uses the CyberArk mobile SDK. On the Settings page in the Identity Administration portal, specify the following settings:Įnter your Zoom domain name. The application opens to the Settings page. On the Add Web App page, click Yes to confirm.Ĭlick Close to exit the Application Catalog. On the Search page, enter the application name in the Search field and click the search button. ![]() In the Identity Administration portal, select Apps & Widgets > Web Apps, then click Add Web Apps. ![]() For information on optional configuration settings available in the Identity Administration portal, see Configure optional application settings.Ī video for how to configure the Zoom template for SSO is also available. The following steps are specific to this application and are required in order to enable SSO. The additional users that Zoom creates based on the SAML response are part of the original Zoom administrator account but they are non-administrative users (they can’t edit Zoom account settings, for example). If the user doesn’t already exist, Zoom creates the user account automatically with the user account received in the SAML response. Once Zoom receives the SAML response from CyberArk Identity, Zoom checks to see if the user already exists. After you’ve created your administrative account in Zoom and configured SSO, you don’t need to register additional users. (In most other applications that use SP-initiated SSO, the application blocks users from logging in directly to the application account.) SP-initiated SSO uses just the domain-specific URL with Zoom, such as where acme is your custom domain. If you configure CyberArk Identity to use SP-initiated SSO to launch Zoom, be aware that you can still log in to your Zoom account using the URL. What to know before configuring SSO for Zoom You also upload the public key certificate in a. p12 file on the application’s Trust page in the Identity Administration portal. If you use your own certificate, you upload the signing certificate and its private key in a. To establish a trusted connection between the web application and CyberArk Identity, you need to have the same signing certificate in both the application and the application settings in the Identity Administration portal. You can either download one from the Identity Administration portal or use your organization’s trusted certificate.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |