The “API Manager” screen can be accessed from the configuration menu.
In this section you can configure those API Managers in which we later want to deploy our APIs. Apigee, Azure API Management, Mulesoft, AWS API Gateway, Kong and WSO2 are the API Managers available for linking.
Clicking on the link button will open a window in which we will be asked for the access information for each of them.
Apigee #
To configure the Apigee API Manager, click on the link button.
Once clicked, a form opens where the fields Username, password and apigee organization must be filled in. In this case, all three fields are mandatory in order to click on the link button and finish the process.
Once the API Manager is linked, the linkage can be edited or removed from these icons.
Figura 48 Editar/Eliminar Apigee
Azure API Management #
To configure the API Manager Azure API Management click on the link button.
Once clicked, a form opens where, in this case, there are two ways to link.
First of all, if you choose the option “Login in browser” you will be redirected to the Azure website to login. Once you have logged into the API Quality website, you must finish linking by filling in the Azure instance name field.
The second option to link is to choose “Login via primary key” and fill in all the mandatory fields that appear with this option which are subscription ID, group name, identifier, API key and URL.
Once the APImanager is linked, the linkage can be edited or removed from these icons.
Mulesoft #
To configure the Mulesoft API Manager click on the link button.
Once clicked, a form opens where the Mulesoft authentication type and Mulesoft organization fields must be filled in. Once the authentication type field is filled in, two more fields appear to be filled in. Depending on what has been chosen, the user name or Client ID must be filled in. The second field to fill in is the password.
In this case, all fields are mandatory in order to be able to click on the link button and finish the process.
Once the API manager is linked, the linkage can be edited or removed from these icons.
AWS API Gateway #
To configure the API manager AWS API Gateway, click on the link button.
Once clicked, a form opens where the AWS ID and AWS Access Key fields must be filled in. In this case, both fields are mandatory to be able to click on the link button and finish the process.
Once the API Manager is linked, the linkage can be edited or removed from these icons.
Kong #
To configure API Manager Kong click on the link button.
If you choose default, no more fields will be displayed.
Once clicked, a form opens where you must fill in the Kong authentication type and URL fields, both of which are mandatory. Depending on the type of authentication chosen, more fields will be displayed.
In the case of choosing JwtAuth you have to fill in the fields algorithm ,jwt key and URL the fields are mandatory to be able to click on the link button and finish the process.
If you choose KeyAuth you must fill in the API key field which is mandatory to be able to click on the link button and finish the process.
In the case of choosing Oauth2 credentials the Client ID, provision key, client secret and scope fields will appear. All of them are mandatory in order to click on the link button and finish the process.
And finally, if BasicAuth is chosen, the user name and password fields must be filled in before clicking on the link button to finish the process.
Once the API Manager is linked, the linkage can be edited or removed from these icons.
WSO2 #
To configure the WSO2 API Manager, click on the link button.
Once clicked, a form opens where the user name, password and URL fields must be filled in. In this case, all three fields are mandatory in order to click on the link button and finish the process.
Once the API Manager is linked, the linkage can be edited or removed from these icons.
Once we have linked the API Manager(s) we want to use to deploy your organization’s APIs, we display all the URLs of the API Managers.
