Extensions
You can configure extensions from . It requires the permission to be enabled.
GET operation
in a specification is used to test connectivity and authentication. If a specification doesn't
include a GET operation, an extension cannot be tested, but it can still be enabled. If you're on
IBM
OpenPages as a Service, wait a few minutes after you enable
the extension and before you test the connection as it may take a few minutes for the egress to be
opened. If you're on IBM
OpenPages on Cloud and the firewall
is not opened, you must contact IBM® support to update
the firewall to allow the connection.Requirements
- OpenAPI specification (JSON, YAML, or YML)
- Authentication information
- Values of server variables (if the specification includes variables)
*.azure.com *.*.services.ai.azure.com *.*.models.ai.azure.com *.openai.azure.com *.lambda-url.*.on.aws *.googleapis.com api.openai.com api.llama.com api.mistral.ai api.gemini.com
For more information on the specification, see the extensions topic for developers.
Enabling and testing connections
A new extension is not enabled by default. You cannot test a connection until you enable the extension from the grid on the Extensions tab.
The first GET operation in a specification is used to test connectivity and
authentication. If a specification doesn't include a GET operation, an extension cannot be tested,
but it can still be enabled.
If you're on IBM
OpenPages as a Service, wait a few minutes after you enable the
extension and before you test the connection as it may take a few minutes for the egress to be
opened.
If you're on IBM
OpenPages on Cloud and the firewall is not opened, you must
contact IBM support to update the firewall to allow the
connection.