Connect API Portal to API Manager
8 minute read
Before you can use API Portal, you must connect it to at least one API Manager. You can also connect API Portal to multiple API Managers to expose APIs centrally in one place.
Connect API Portal to a single API Manager
Before you can use API Portal, you must connect it to at least one API Manager. By default, API Portal uses ports
443. You can access the ports using a browser.
To connect API Portal to API Manager:
- Log in to the Joomla! Administrator Interface (JAI) (
- Select Components > API Portal > API Manager.
- Enter a public name for the API Manager. This name is shown to your API consumers in API Portal when listing the APIs and applications for this API Manager.
- Enter your API Manager host and port. The default port is
- In TLS Certificate Validation, select an option to validate HTTPS connections. The default is no validation. You can choose to validate the TLS certificate only, or the TLS certificate and the certificate host name.
- If you choose to validate the TLS certificate, in Certificate, choose and upload the root API Manager certificate. This certificate is used to validate the API Manager server certificate when API Portal sends a request to API Manager. You can check which certificate API Portal uses in Current certificate.
- Enter a tag for this API Manager. You can use this tag to filter APIs that come from this particular API Manager instance, for example, to display APIs from different API Managers on different menus in API Portal.
- Click Save.
API Portal is now connected to API Manager.
To log into API Portal you must have a user configured in API Manager. For more information, see Manage users. Note that, by default, only users with Organization administrator or User roles are allowed to login to API Portal.
Connect API Portal to multiple API Managers
This section describes how to configure API Portal to connect to more than one API Manager.
APIs are often hosted in several API Manager instances, for example, in multiple environments (sandbox, testing, production) or in multiple API Catalogs (for example, for internal users and for external users). You can configure API Portal to connect to multiple API Managers so that the exposed APIs can be explored centrally in one place.
For example, you can configure API Portal as a centralized catalog presenting APIs across all environments:
NoteThis type of portal is recommended only for internal purposes and internal users.
Alternatively, API Portal can pull APIs from different deployments. For example, you could host one API Manager with non-business critical APIs in a cloud, and another API Manager containing the APIs on confidential data on-premise. A single API Portal can connect to both deployments, and expose the APIs as configured in each API Manager:
API Managers and API Catalogs are configured normally, each API Manager controlling how the APIs in it are exposed.
One of the API Managers is assigned as a master API Manager, and it controls all user operations, such as signing up and signing in to API Portal, forgotten password, and updates to user profiles. The rest of the API Managers act as slaves that automatically upon user login call the master API Manager using a specific policy for the user information, replicate the user, and create API Portal user session cookies.
Other operations in API Portal, such as managing organizations, APIs, and applications, are done separately for each API Manager as usual.
For better performance, you can configure API Portal to cache the APIs from all API Managers in a Redis cache. Instead of directly querying each API Manager separately, API Portal reads the APIs from the cache. This improves the performance, especially when there are hundreds of APIs.
Example login flow with multiple API Managers
- A user tries to log in to API Portal.
- API Portal sends a login request including the login credentials to all API Managers.
- API Manager finds the user in its user registry, and allows the user to log in.
- If a slave API Manager does not find the user, it triggers a specific policy that calls to the master API Manager to query for the user.
- If the master API Manager finds the user, it returns all the user parameters (name, email, organization) to the slave API Manager.
- The slave API Manager creates a session cookie for the user and returns that to API Portal along with the user’s organization and APIs and applications in it.
- The user is logged in to API Portal .
- When the user is logged out, the session is destroyed on the slave API Managers.
After a successful login, the user can see APIs and applications assigned to the user’s organization in all API Manager instances. For example, the user A belongs to organization X that has the following configurations on two API Managers:
Master API Manager
- Organization X has application F that is shared with the user A.
- Organization X has APIs C and D that are both assigned to application F.
Slave API Manager
- Organization X has application Q that is shared with the user A.
- Organization X has APIs G and H that are both assigned to application Q.
This means that when API Portal is connected to both API Managers, user A sees the APIs C, D, G, and H listed in API Catalog, and applications F and Q on the Applications page. If API Portal was only connected to the master API Manager, user A would see only APIs C and D, and application F.
Before you can connect API Portal to multiple API Managers, ensure that:
- All the API Manager instances are configured and running.
- All the organizations are created on all API Managers. Ensure that the name of an organization is identical across all instances.
- Users are created and assigned to organizations on the master API Manager.
Configure synchronization policies for API Managers
The slave API Managers communicate with the master API Manager using an external identity provider policy. A sample policy container
AuthoToMasterDynamicOrg.xml is included in the API Portal installation package available from Axway Support.
You must import the policy container to Policy Studio, configure the sample policies to point to your master API Manager, configure your environment settings, and deploy the configuration to your slave API Manager. For more information on working in Policy Studio, see the Develop in Policy Studio.
You must create a separate project for each slave API Manager to use separate connections when deploying the configured policy.
Import and configure the policies
- In Policy Studio, create a new project from the API Gateway instance running the slave API Manager you want to configure.
- Click File > Import > Import Configuration Fragment, and import
- In the Policy Studio node tree, click Policies > Sample policies > AuthoToMaster, and open the policy AuthenticateToMaster.
- Double-click the Login to Master routing filter, and change the IP address and port in URL to point to your master API Manager.
- On the Settings tab, under Redirect, ensure that Follow redirects is not selected and click Finish.
- Open the policy Get Current Info, and repeat steps 4 and 5 on the get current info routing filter.
- Open the policy GetOrganizationName, and repeat steps 4 and 5 on the get organization name routing filter.
Configure environment settings
In the Policy Studio node tree, click Environment Configuration > Listeners > API Gateway > API Portal > Ports.
Open the configured port, go to the Mutual Authentication tab, and check that Ignore client certificates is selected.
In the node tree, click Environment Configuration > Listeners > API Gateway > API Portal > Paths., and under
/api/portal/, double-click API Manager API v1.3 or API Manager API v1.4, depending on your API Portal version.
Add a new servlet property. The version of the API can be
1.4depending on your API Portal version.
- Value: the login URL of the master API Manager (for example,
If you already have a servlet property, you can simply edit its value. If you list multiple URLs, separate them with a comma.
In the node tree, click Server Settings > General, and ensure that Server’s SSL cert’s name must match name of requested server is not selected.
Click Server Settings > API Manager > Identity Provider, and select Use external identity provider.
Set Account authentication policy to the AuthenticateToMaster policy and Account information policy to Get Current Info, and click Save.
Deploy the configuration to API Gateway.
Configure the connection to slave API Managers
- Log in to JAI.
- Connect to your master API Manager, see Connect API Portal to a single API Manager.
- Click Components > API Portal > Additional API Managers.
- Enter the public label (for example,
Environment) for the API Managers. This label is shown to your API consumers in API Portal when listing the APIs and applications for multiple API Managers.
- In Login Failure Policy, select how failed logins are handled.
- Click + to add a slave API Manager, and enter a public name for it (for example,
Production). This name is shown to your API consumers in API Portal when listing the APIs and applications for this API Manager.
- Enter the host IP address and port of the slave API Manager.
- Configure the remaining settings and click Save.
- Repeat to add additional slave API Managers.
API Portal is now connected to multiple API Managers.
To log in in to API Portal you must have a user configured in API Manager. For more information, see Manage users. Note that, by default, only users with Organization administrator or User roles are allowed to login to API Portal.
Watch this video to learn more about how to connect API Portal to multiple API Managers.
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.