With a properly deployed SSO solution, you can do the following:

• Eliminate weak passwords for each cloud application

• Streamline the secured access process

• Provide one-click access to cloud applications

To configure Okta SSO, use Cisco vManage to enable an identity provider and generate a Security Assertion Markup Language (SAML) metadata file.

From Cisco vManage Release 20.10.1, you can use Add New IDP Settings to configure up to three IdPs. For more information on integrating with multiple IdPs, see the chapter Configure Multiple IdPs.

1. From the Cisco vManage menu, choose Administration > Settings.

2. Click Identity Provider Settings and then click Edit.

3. Click Enabled.

4. Click Click here to download the SAML metadata and save the contents in a text file. This data is used for configuring Okta.

5. From the metadata that is displayed, make a note of the following information that you need for configuring Okta with Cisco vManage:

   • Entity ID

   • Signing certificate

   • Encryption certificate

   • Logout URL

   • Login URL

   Note	Administrators can set up SSO using a single Entity ID only. Cisco vManage doesn't support more than one Entity ID while setting up SSO.

6. In the Upload Identity Provider Metadata section, click Select a File to upload the IdP metadata file.

7. Click Save.

Note	This procedure involves a third-party website. The details are subject to change.

To configure SSO on the Okta website:

1. Log in to the Okta website.

   Note	Each IdP application gets a customized URL from Okta for logging in to the Okta website.

2. Create a username using your email address.

3. To add Cisco vManage as an SSO application, from the Cisco vManage menu, click Admin.

4. Check the upper-left corner to ensure that it shows the Classic UI view on Okta.

5. If it shows Developer Console, click the down triangle to choose the Classic UI.

6. Click Add Application under Shortcuts to the right to go to the next window, and then click Create New Application on the pop-up window.

7. Choose Web for the platform, and choose SAML 2.0 as the Sign on Method.

8. Click Create.

9. Enter a string as Application name.

10. (Optional): Upload a logo, and then click Next.

11. On the SAML Settings for Single sign on URL section, set the value to the samlLoginResponse URL from the downloaded metadata from Cisco vManage.

12. Check the Use this for Recipient URL and Destination URL check box.

13. Copy the entityID string and paste it in the Audience URI (SP Entity ID) field.

    The value can be an IP address or the name of the Cisco vManage site.

14. For Default RelayState, leave empty.

15. For Name ID format, choose EmailAddress.

16. For Application username, choose Okta username.

17. For Show Advanced Settings, enter the fields as indicated below.

    Table 2. Fields for Show Advanced Settings

    Component	Value	Configuration
    Response	Signed	Not applicable
    Assertion Signature	Signed	Not applicable
    Signature Algorithm	RSA-SHA256	Not applicable
    Digest Algorithm	SHA256	Not applicable
    Assertion Encryption	Encrypted	Not applicable
    Encryption Algorithm	AES256-CBC	Not applicable
    Key Transport Algorithm	RSA-OAEP	Not applicable
    Encryption Certificate	Not applicable	Copy the encryption certificate from the metadata you downloaded. Go to www.samltool.com and click X.509 CERTS, paste there. Click Format X.509 Certificate. Ensure to remove the last empty line and then save the output (X.509.cert with header) into a text file encryption.cer. Upload the file. Mozilla Firefox may not allow you to do the upload. Instead, you can use Google Chrome. You should see the certificate information after uploading to Okta.
    Enable Single Logout		Ensure that this is checked.
    Single Logout URL		Get from the metadata.
    Service provider Issuer		Use the entityID from the metadata.
    Signature Certificate		Obtain from the metadata. Format the signature certificate using www.samltool.com as described. Save to a file, for example, signing.cer and upload.
    Authentication context class	X.509 Certificate	Not applicable
    Honor Force Authentication	Yes	Not applicable
    SAML issuer ID string	SAML issuer ID string	Not applicable
    Attribute Statements	Field: Name	Value: Username
    	Field: Name format (optional)	Value: Unspecified
    	Field: Value	Value: user.login
    Group Attribute Statements	Field: Name	Value: Groups
    	Field: Name format (optional)	Value: Unspecified
    	Field: Matches regex	Value: .*

    Note	It is mandatory to use the two strings, Username and Groups, exactly as shown above. Otherwise, you may be logged in with the default group of Basic.

18. Click Next.

19. For Application Type, check This is an internal app that we have created (optional).

20. Click Finish. This brings you to the Okta application window.

21. Click View Setup Instructions.

22. Copy the IdP metadata.

23. In Cisco vManage, navigate to Identity Provider Settings > Upload Identity Provider Metadata, paste the IdP metadata, and click Save.

24. In addition to copy-and-pasting the contents of a file with IdP metadata, you can also upload a file directly using the Select a file option.

Note	This procedure involves a third-party website. The details are subject to change.

To assign users to the application on the Okta website:

1. On the Okta application window, navigate to Assignments > People > Assign.

2. Choose Assign to people from the drop-down menu.

3. Click Assign next to the user(s) you chose and click Done.

4. To add a user, click Directory > Add Person.

5. Click Save.

Note	This procedure involves a third-party website. The details are subject to change.

Step 1 - Import ADFS Metadata to Cisco vManage:

1. Download the ADFS metadata file, typically from the ADFS URL: https://<your ADFS FQDN or IP>/FederationMetadata/2007-06/FederationMetadata.xml.

2. Save the file as adfs_metadata.txt.

3. From the Cisco vManage menu, choose Administration > Settings > Identity Provider Settings > Enable, and then upload adfs_metadata.txt to Cisco vManage.

   Step 2 - Export Cisco vManage Metadata to ADFS:

4. With Identity Provider Settings enabled, Click here to download SAML metadata and save the contents to a file, which is typically 192.168.1.15_saml_metadata.xml.

5. After the SAML metadata is downloaded, verify that the signing certificate and the signature certificate are the same.

   1. If the signing certificate and the signature certificate are the same, proceed to Step 6 to edit the Cisco vManage metadata file.

   2. If the signing certificate and the signature certificate are not the same, use the signature certificate for the remaining steps, not the signing certificate.

6. Edit the Cisco vManage metadata file by deleting everything from <ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#"> to </ds:Signature>.

7. Edit the Cisco vManage metadata file by deleting everything from <md:KeyDescriptor use="encryption"> to </md:KeyDescriptor>.

8. Import the new modified Cisco vManage metadata file into ADFS, and enter the entityID as Display Name.

9. Click Next until the end.

10. Open Edit Claim Rule, and add the following four new custom rules in the exact sequence:

    @RuleName = "sAMAccountName as Username" c:[Type == "http://schemas.microsoft.com/ws/2008/06/identity/claims/windowsaccountname", Issuer == "AD AUTHORITY"]=> issue(store = "Active Directory", types = ("Username"), query = ";sAMAccountName;{0}", param = c.Value);

    @RuleName = "sAMAccountName as NameID" c:[Type == "http://schemas.microsoft.com/ws/2008/06/identity/claims/windowsaccountname", Issuer == "AD AUTHORITY"] => issue(store = "Active Directory", types = ("http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier"), query = ";sAMAccountName;{0}", param = c.Value);

    @RuleName = "Get User Groups and save in temp/variable" c:[Type == "http://schemas.microsoft.com/ws/2008/06/identity/claims/windowsaccountname", Issuer == "AD AUTHORITY"] => add(store = "Active Directory", types = ("http://temp/variable1"), query = ";tokenGroups;{0}", param = c.Value);

    @RuleName = "Parse temp/variable1 and Send Groups Membership" c:[Type == "http://temp/variable1", Value =~ "(?i)^SSO-"] => issue(Type = "Groups", Value = RegExReplace(c.Value, "SSO-", ""));

11. Verify the final result.

12. In the Active Directory, create the following two security groups: SSO-Netadmin and SSO-Operator.

    Note	If you are using different naming convention for the two security groups, then you have to modify the regular expression value "(?i)^SSO-" in the step above.

    Any active directory users who are not members of the two groups will only have Basic access to Cisco vManage.

Note	This procedure involves a third-party website. The details are subject to change.

To add ADFS relying party trust manually:

1. Launch AD FS 2.0 Management.

2. Navigate to Trust Relationships > Relying Party Trusts.

3. Click Action > Add Relying Party Trust.

4. Click Start.

5. Choose Enter data about the relying party manually, and click Next.

6. Choose Display name and Notes, and then click Next.

7. Choose AD FS 2.0 profile, and click Next.

8. Click Next to skip Configure Certificate page.

9. Click Enable support for the SAML 2.0 Webs So protocol.

10. Open a text editor, and open the 10.10.10.15_saml_metadata.xml file.

11. Copy the vale of the Location attribute for AssertionConsumerService, and paste it into the Relying party SAML 2.0 SSO service URL text box.

12. Click Next.

13. Copy the value of the entityID attribute, and paste it into the Relying party trust identifiers text box.

14. Click Add, and click Next.

15. Click Next to skip to the Configure Multi-factor Authentication Now section.

16. Choose Permit all users to access this relying party, and click Next.

17. Click Next to skip to the Ready to Add Trust section.

18. Click Close.

19. Open Edit Claim Rules window, and add the following four new custom rules in this order:

    • @RuleName = "sAMAccountName as Username" c:[Type == "http://schemas.microsoft.com/ws/2008/06/identity/claims/windowsaccountname", Issuer == "AD AUTHORITY"]=> issue(store = "Active Directory", types = ("Username"), query = ";sAMAccountName;{0}", param = c.Value);

    • @RuleName = "sAMAccountName as NameID" c:[Type == "http://schemas.microsoft.com/ws/2008/06/identity/claims/windowsaccountname", Issuer == "AD AUTHORITY"] => issue(store = "Active Directory", types = ("http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier"), query = ";sAMAccountName;{0}", param = c.Value);

    • @RuleName = "Get User Groups and save in temp/variable" c:[Type == "http://schemas.microsoft.com/ws/2008/06/identity/claims/windowsaccountname", Issuer == "AD AUTHORITY"] => add(store = "Active Directory", types = ("http://temp/variable1"), query = ";tokenGroups;{0}", param = c.Value);

    • @RuleName = "Parse temp/variable1 and Send Groups Membership" c:[Type == "http://temp/variable1", Value =~ "(?i)^SSO-"]=> issue(Type = "Groups", Value = RegExReplace(c.Value, "SSO-", ""));

20. Open the Edit Claim Rules window, and verify that the rules display in Assurance Transform Rules.

21. Click Finish.

22. Open the Properties window of the newly created Relying Party Trust, and click Signature.

23. Click Add, and add the Signing.cer created in Step 6.

24. In the Active Directory, click General, and enter the following two security groups in the Group name text box:

    SSO-Netadmin

    SSO-Operator

    Note	If you use a different naming convention for the two security groups, then you have to modify the Regular expression value for (?i)^SSO- mentioned in Step 19.

    Note	Any active directory user who is NOT a member of these two groups, will only have Basic access to Cisco vManage.

Note	This procedure involves a third-party website. The details are subject to change.

To configure PingID:

1. Log in to the PingID administration portal.

2. Create a username using your email address.

3. Click the Applications.

4. Click Add Application and choose New SAML Application.

   In the Application Details section, Application Name, Application Description, and Category are all required fields.

   For logos and icons, PNG is the only accepted graphics format.

5. Click Continue to Next Step.

   The Application Configuration section appears.

6. Make sure that you choose I have the SAML configuration.

7. Under the You will need to download this SAML metadata to configure the application section, configure the following fields:

   1. For Signing Certificate, use the drop-down menu, PingOne Account Origination Certificate.

   2. Click Download next to SAML Metadata to save the PingOne IdP metadata into a file.

   3. Later, you need to import the PingOne IdP metadata file into Cisco vManage to complete the SSO configuration.

      1. From the Cisco vManage menu, choose Administration > Settings.

      2. Click Identity Provider Settings > Upload Identity Provider Metadata to import the saved PingOne IdP metadata file into Cisco vManage.

      3. Click Save.

8. Under the Provide SAML details about the application you are connecting to section, configure the following fields:

   1. For Protocol Version, click SAMLv2.0.

   2. On Upload Metadata, click Select File to upload the saved Cisco vManage SAML metadata file to PingID.

      PingID should be able to decode the metadata file and fill in the other fields.

   3. Verify that the following fields and values are entered correctly.

   Field	Value
   Assertion Consumer Service (ACS)	<vManage_URL>/samlLoginResponse
   Entity ID	IP address of Cisco vManage
   Single Logout Endpoint	<vManage_URL>/samlLogoutResponse
   Single Logout Binding Type	Redirect
   Primary Verification Certificate	Name of the certificate
   Encrypt Assertion	(Optional) If you do not encrypt the assertion, you might be prone to assertion replay attacks and other vulnerabilities.
   Encryption Certification	Name of the certificate
   Encryption Algorithm	(Optional) AES_256
   Transport Algorithm	RSA_OAEP
   Signing Algorithm	RSA_SHA256
   Force Re-authentication	False

9. Click Continue to Next Step.

10. In the SSO Attribute Mapping section, configure the following fields:

    1. Click Add new attribute to add the following attributes:

       1. Add Application Attribute as Username.

       2. Set Identity Bridge Attribute or Literal Value Value to Email.

       3. Check the Required box.

       4. Add another Application Attribute as Groups.

       5. Check the Required check box, and then click on Advanced.

       6. In the IDP Attribute Name or Literal Value section, click memberOf, and in Function, click GetLocalPartFromEmail.

    2. Click Save.

11. Click Continue to Next Step to configure the Group Access.

12. Click Continue to Next Step.

13. Before clicking Finish, ensure that the settings are all correct.

1. From the Cisco vManage menu, choose Administration > Settings.

2. Click Identity Provider Settings and then click Edit.

3. Click Enabled.

4. Click Click here to download the SAML metadata and save the contents in a text file.

Note	This procedure involves a third-party website. The details are subject to change.

1. Log in to the Azure AD portal.

2. Create an enterprise application in Azure services.

   An enterprise application integrates Azure AD with Cisco vManage. To create a new application, you must use the Non-gallery application.

3. Upload the SAML metadata file that you downloaded from Cisco vManage.

4. Configure the following fields according to the instructions available for the User Attributes & Claims section in the Azure AD portal.

   Table 3. Attributes and Claims

   Field	Value
   Unique User Identifier (Name ID)	user.mail
   Groups	netadmin
   userprincipalname	user.userprincipalname

5. Download the federation metadata XML (Azure AD metadata) file.

6. From the Cisco vManage menu, choose Administration > Settings.

7. Choose Identity Provider Settings > Upload Identity Provider Metadata to import the saved Azure AD metadata file into Cisco vManage.

8. Click Save.

Minimum supported releases: Cisco IOS XE Release 17.8.1a and Cisco vManage Release 20.8.1

1. Log in to the Azure AD portal.

2. View the log of the authorized SSO logins.

Minimum supported release: Cisco vManage Release 20.10.1

With this feature, you can now configure more than one IdP per tenant in Cisco vManage. This feature supports both single-tenant and multitenant environments.

You can configure up to three IdPs per tenant and a maximum of three IdPs per the provider.

The following fields are added in Cisco vManage Administration > Settings > Identity Provider Settings for configuring multiple IdPs:

• Add New IDP Settings

• IDP Name

• Domain

You can also edit or delete an IdP name and domain name.

For more information on configuring multiple IdPs, see Configure Multiple IdPs.

Minimum supported release: Cisco vManage Release 20.10.1

• You can configure only three IdPs in a single-tenant deployment and three IdPs per tenant in a multitenancy deployment.

Minimum supported release: Cisco vManage Release 20.10.1

The following are potential use cases for integrating with multiple IdPs:

• An end user (tenant) requires different types of user access for employees versus contractors.

• An end user requires different types of user access for different functions within the organization.

• An end user requires access to the same IdP, but has a different email address.

Minimum supported release: Cisco vManage Release 20.10.1

The following workflow is for configuring multiple IdPs. For more information on enabling an IdP, see Enable an Identity Provider in Cisco vManage.

1. From the Cisco vManage menu, choose Administration > Settings.

2. Click Identity Provider Settings and choose Edit.

3. Click Add New IDP Settings.

   Note	After three IdPs are configured, the Add New IDP Settings option is no longer displayed.

4. Click the toggle button to switch between enabling and disabling IdP settings while retaining the existing configuration.

5. Click IDP Name and enter a unique name for your IdP.

   Examples:

   • okta

   • idp1

   • provider

   • msp

   You can configure a maximum of three IdPs.

   Note	You cannot map the same domain to multiple IdPs, but you can use the same IdP for multiple domains.

6. Click Domain and enter a unique domain name for your IdP, for example, okta.com.

   If the domain name already exists, Cisco vManage generates an error message.

   Note	You can also add a domain later to an existing IdP.

7. In the Upload Identity Provider Metadata section, upload the SAML metadata file you downloaded from your IdP.

8. Click Save.

9. After you configure a new IdP name, domain, and sign out of your current Cisco vManage session, you are redirected to a unified SAML login page.

10. In the unified SAML login page, if you require local authentication, remove the login.html portion of the URL. This redirects you to the local authentication page.

    Note	A user ID must be in an email address format, for example, john@mystore.com.

11. In the unified SAML login page, enter the SSO credentials for your IdP.

    Note	You are redirected to the unified SAML login page each time you access Cisco vManage after configuring a new IdP name and domain.

Minimum supported release: Cisco vManage Release 20.10.1

1. From the Cisco vManage menu, choose Administration > Settings.

2. Click Identity Provider Settings and then click View.

3. Verify the configured IdP and the corresponding domain.

Minimum supported release: Cisco vManage Release 20.10.1

For troubleshooting integration issues with multiple IdPs, you can access the log files at:

• /var/log/nms/vmanage-server.log is the log file for enabling and disabling IdP.

• /var/log/nms/vmanage-sso.log is the SSO-specific log file.