Cisco vManage SSO login using Azure AD
Cisco vManage SSO login using Azure AD
Performing network administration operations requires access to multiple websites or applications. Multiple credentials are required to access each of these websites or applications. Their credentials might have been forgotten or stolen.
Fig 1.1-Cisco vManage SSO login using Azure AD |
One set of credentials can be used to access multiple applications or websites using the single sign-on technology (SSO).
- Identity provider (IdP): This system keeps user data, as well as maintains and supports authentication mechanisms such as Okta, ADFS, PingID, and Azure AD.
- Service provider: This system hosts the desired website or application, such as Cisco vManage.
- Users: Individuals who have an account with the IdP and the service provider.
vManage steps
Step 1: Login to the vManage portal, Navigate to Administrator --> Settings and search for Identity Provider Settings as shown below
Step 2: Enable and check the below image to download the SAML meta data
Step 3: The file will be in TXT format. Now it is required to the upload this TXT file to the Azure.
Azure steps
Step 1: Log in to the Azure AD portal.
Step 2: Create an enterprise application in Azure services.
Step 1: Login to the vManage portal, Navigate to Administrator --> Settings and search for Identity Provider Settings as shown below
Fig 1.2- vManage Portal |
Step 2: Enable and check the below image to download the SAML meta data
Fig 1.3- vManage Portal |
Step 3: The file will be in TXT format. Now it is required to the upload this TXT file to the Azure.
Azure steps
Step 1: Log in to the Azure AD portal.
Step 2: Create an enterprise application in Azure services.
Fig 1.4- Azure Portal |
When you are creating the new application here, make sure select the option " Create your own application"
Step 3: An enterprise application integrates Azure AD with Cisco vManage. To create a new application, you must use the Non-gallery application.
Step 3: An enterprise application integrates Azure AD with Cisco vManage. To create a new application, you must use the Non-gallery application.
Fig 1.5- Azure Portal |
Step 4: Assign user and roles as we are doing for the other applications
Step 5: "Setup the single sign on option" Upload the SAML metadata file that you downloaded from Cisco vManage.
Step 6: From the single Sign-on Menu, we need to select SAML option
Step 7: Download the federation metadata XML (Azure AD metadata) file
Step 5: "Setup the single sign on option" Upload the SAML metadata file that you downloaded from Cisco vManage.
Step 6: From the single Sign-on Menu, we need to select SAML option
Step 7: Download the federation metadata XML (Azure AD metadata) file
Fig 1.6- Azure Portal |
Now we need to go to the vManage again to upload the federation metadata
Step 1: From the Cisco vManage menu, choose Administration > Settings
Step 2: Choose Identity Provider Settings > Upload Identity Provider Metadata to import the saved Azure AD metadata file into Cisco vManage. ( Select a file on the right hand side and upload that from your desktop)
Step 3: Click Save.
Continue Reading...
++++++++++++++++++++++++++++++++++++++++++++++++++++
Cisco SDWAN: vManage as Management Plane - The Network DNA
vBond in Cisco Viptela SDWAN - The Network DNA
Cisco Viptela SD-WAN : vSmart as a Control Plane - The Network DNA
Cisco SDWAN Resources - The Network DNA
++++++++++++++++++++++++++++++++++++++++++++++++++++
Step 1: From the Cisco vManage menu, choose Administration > Settings
Fig 1.7- vManage Portal |
Step 2: Choose Identity Provider Settings > Upload Identity Provider Metadata to import the saved Azure AD metadata file into Cisco vManage. ( Select a file on the right hand side and upload that from your desktop)
Fig 1.8- vManage Portal |
Continue Reading...
++++++++++++++++++++++++++++++++++++++++++++++++++++
Cisco SDWAN: vManage as Management Plane - The Network DNA
vBond in Cisco Viptela SDWAN - The Network DNA
Cisco Viptela SD-WAN : vSmart as a Control Plane - The Network DNA
Cisco SDWAN Resources - The Network DNA
++++++++++++++++++++++++++++++++++++++++++++++++++++