Registering new API Client Applications

As part of the Cisco API security migration, it is necessary to register new client applications on the Mulesoft API console. In this section you will find the steps to register such applications and request access to both CiscoXaaXAPI and CiscoPartyAPI.

Requesting Access to CiscoXaaSAPI

Production Environment

Go to the developer portal at the following URL: https://anypoint.mulesoft.com/exchange/portals/cisco-prod/
First, request access to the following API instance: CiscoXaaSAPI.
Click Request API Access in the left menu and then click Request Access.
In the Request access dialog box, select the corresponding API instance: CiscoXaaSAPI.
In the Application drop-down list select Create New Application.
Enter the application name. As we are registering the application for the production environment, you can use the following application name: Cisco API PMI - Prod.
Select the following options: Resource Owner Grant, Client Credentials Grant and Automatically register the redirect URIs for API Notebook and API Console.
Click Create.
If any SLA tier is defined for the API, select the SLA tier from the drop-down list. (Bronze-Quota, Siver-Quota or Gold-Quota).
Click Request Access.

Important: The request needs to be approved by the API owner. The migration process must not start until the status of your request is Approved.

Now, go to My applications in the top menu and click the application that you have just created. ( Cisco API PIM - Prod). You can check the status of your request by clicking on the icon next to the listed API for which you requested access.

Then, copy the Client ID and Client Secret that have been generated for the application. You will need to use these credentials to configure the parameters for the production environment in the Connect Distributor Portal (clientID and clientSecret)

Test Environment

Once you have requested access for CiscoXaaSAPI and obtained the credentials for the production environment (PMI), you must repeat the steps above to register the client application for the test environment (POE). The steps are the same as explained above, but this time you will need to use the following name for the new application (step 6): Cisco API POE - Test.

Once you have registered the application, go to My applications in the top menu and click the application that you have just created. ( Cisco API PIM - Test). You can check the status of your request by clicking on the icon next to the listed API for which you requested access.

Then, copy the Client ID and Client Secret that have been generated for the application. You will need to use these credentials to configure the parameters for the test environment in the Connect Distributor Portal (clientID_test and clientSecret_test).

Requesting Access to CiscoPartyAPI

CiscoPartyAPI is used for the validation of resellers (DRAN). For this API, you can use the same set of credentials that you obtained previously when you registered the client application for CiscoXaaSAPI. Complete the following steps:

Go to the developer portal at the following URL: https://anypoint.mulesoft.com/exchange/portals/cisco-prod/
First, request access to the following API instance. CiscoPartyAPI.
Click Request API Access in the left menu and then click Request Access.
In the Request access dialog box, select the corresponding API instance: CiscoPartyAPI.
In the Application drop-down list select one of the applications that you created previously for CiscoXaaSAPI: Cisco API POE - Test or Cisco API PMI - Prod. As you can see, in this case, we will be using the same set of credentials both for CiscoXaaSAPI and CiscoPartyAPI. You just need to select the application for the corresponding environment.
Click Create.
If any SLA tier is defined for the API, select the SLA tier from the drop-down list. (Bronze-Quota, Siver-Quota or Gold-Quota).
Click Request Access.

Once you have requested access to CiscoPartyAPI in a production environment (PMI), you must repeat the steps above to request access in a test environment (POE). This is done by selecting the corresponding application in each case (step 5).