SAML SSO Okta Identity Provider SAML SSO Okta Identity Provider 2 Introduction 2 Configure Okta as Identity Provider 2 Enable SAML SSO on Unified Communications Applications 4 Test SSO on Okta 4
Revised: October 6, 2017, SAML SSO Okta Identity Provider Note Refer to the SAML SSO Deployment Guide for Cisco Unified Communications Applications for your release to find out if Okta has been tested with your release. Introduction Single sign-on (SSO) is a session or user authentication process that enables a user to provide credentials to access one or more applications. The process authenticates the user for all applications they have been given rights to and eliminates further prompts when they switch applications during a particular session. For more information about the SAML SSO Solution, see: SAML SSO Deployment Guide for Cisco Unified Communications Applications. This document provides steps to configure Okta as SAML SSO Identity Provider (IdP) for Cisco Unified Communications Manager (Unified CM), Cisco Unified Communications Manager IM and Presence Service (IM and Presence Service), Cisco Unity Connection, or Cisco Prime Collaboration Assurance. Configure Okta as Identity Provider Use this procedure to configure Okta as the SAML SSO Identity Provider (IdP) for Cisco Unified Communications Manager. Okta is a cloud-hosted IdP. SAML SSO can be enabled using Okta IdP with the cluster-wide option only. The per node option is not available for Okta. Note For details on how to configure SAML SSO on Cisco Unified Communications Manager, refer to the SAML SSO Deployment Guide at https://www.cisco.com/c/en/us/support/unified-communications/ unified-communications-manager-callmanager/products-maintenance-guides-list.html. Procedure Step 1 Step 2 Step 3 Step 4 Log in to the Service Provider (Cisco Unified Communications Manager) and download the metadata XML file. Log in to the Okta server user interface and click Admin tab. From the Okta dashboard, select Applications > Applications. From the Applications window, click the Add Application button. 2
Step 5 Step 6 Step 7 Step 8 Step 9 Step 10 Various options to create an application or to choose from existing applications appear. Click Create New App to use wizard to create new application integration. On the Create a New Application Integration window, from the Platform drop-down list, choose Web and for the Sign On method field, choose SAML 2.0. Click Create. Enter a name for the application and click Next. On the Create SAML Integration window, enter the details for fields of the General Settings tab, and click Next. Enter details for the following mandatory fields for SAML Settings. These details are available in the metadata XML file that you downloaded from the Service Provider. Single sign on URL From the metadata file, enter the SSO URL of the publisher node. You can find this by searching for the information on index 0 of the AssertionConsumerService and enter the details for this field. Use this for Recipient URL and Destination URL Check this option to enable matching of the recipient and destination URLs. Allow this app to request other SSO URLs Check this option if you have multiple nodes in your UC deployment and you want to allow requests from other SSO URLs besides the publisher. Requestable SSO URLs This field appears only if you check the above check box. You can enter SSO URLS for your other nodes. You can find the ACS URLs in the metadata file by searching for all the AssertionConsumerService (ACS) addresses that use the HTTP-POST Binding. Add those details for this field. Click the Add Another button to add multiple URLs. Note You do not need to add HTTP-Redirect URLs to this field. Audience URI (SP Identity ID) From the metadata file, search for the entityid address and enter the details for this field. Name ID Format Choose Transient from this drop-down list. Application username Choose the username format that matches the UserID field that is available in the Cisco Unified Communications Manager cluster. Step 11 (Optional) Enter the attribute UID to the Cisco Unified Communications Manager cluster. Note Ensure that the attribute UID value matches the userid field value that is available in Cisco Unified CM Administration on the User Management > End User page. Following is an example where the userid is mapped to samaccountname via a UID string of String.substringBefore(user.email, "@"). Figure 1: Sample UID Mapping 3
Step 12 Step 13 Step 14 Step 15 On the Feedback tab, select I'm a software vendor. I'd like to integrate my app with Okta and click Finish. On the Import tab, assign the users or groups that you want to enable, and click Done. On the Sign On tab, click the Identity Provider metadata link to download the Okta metadata file. Open the downloaded metadata file, change the two lines of NameIDFormat to <md:nameidformat>urn:oasis:names:tc:saml:2.0:nameid-format:transient</md:nameidformat>, and then save the file. Enable SAML SSO on Unified Communications Applications When you have configured the IdP appropriately, follow these steps to enable SSO. Procedure Step 1 Navigate to the following page for each application: Cisco Unified Communications Manager Using a web browser, sign in to Unified CM as administrator, and navigate to System > SAML Single Sign On. Cisco Unified Communications Manager IM and Presence Service Using a web browser, sign in to Unified CM as administrator, and navigate to System > SAML Single Sign On. Cisco Unity Connection Using a web browser, sign in to Cisco Unity Connection as administrator, and navigate to System Settings > SAML Single Sign On. Cisco Prime Collaboration Assurance Using a web browser, sign in to Prime Collaboration Assurance as globaladmin, and navigate to Administration > System Setup > Single Sign On. Step 2 Click Enable SAML SSO and follow the steps. Note With Okta, you must use a Cluster wide agreement (one metadata file per cluster). Okta will not work with per node agreements. Note For detailed SAML SSO configuration steps, refer to the SAML SSO Deployment Guide for Cisco Unified Communications Applications. Test SSO on Okta After you have configured SAML SSO on both Okta and Cisco Unified Communications Manager, test the SSO connection. Procedure Step 1 Log in to Okta to authenticate the Okta service. 4
Step 2 Step 3 Step 4 A confirmation message, showing that the SSO configuration is successful, appears. Click Close and then click Finish Close the web browser and wait for a couple of minutes for the SAML SSO configuration changes to take effect on Cisco Unified Communications Manager. Enter the Cisco Unified Communications Manager URL in the address bar of the web browser to verify that SSO is enabled. The Recovery URL to bypass Single Sign On (SSO) link appears below the Cisco Unified Communications Manager link. The Recovery URL to bypass Single Sign On (SSO) link appears when the SSO is enabled. 5
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version of the UNIX operating system. All rights reserved. Copyright 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED AS IS" WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental. Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: http:// www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R) 2017 Cisco Systems, Inc. All rights reserved.
Americas Headquarters Cisco Systems, Inc. San Jose, CA 95134-1706 USA Asia Pacific Headquarters Cisco Systems (USA) Pte. Ltd. Singapore Europe Headquarters Cisco Systems International BV Amsterdam, The Netherlands Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco Website at www.cisco.com/go/offices.