I just edited or deleted my spec, document, page, or snippet. Why don’t I immediately see these changes live in the Dev Portal?
If you recently viewed the related content, your browser might be serving a cached version of the page. To fix this, you can clear your browser cache and refresh the page.
How do I allow developers to view multiple versions of an API in the Dev Portal?
Use the /apis/{apiId}/versions endpoint to publish multiple versions of an API. Developers can then select which API version to view in the Dev Portal spec renderer. Each version reflects how the endpoints were documented at a specific time. It doesn’t reflect the actual implementation, which will usually align with the latest version. Changing the version in the dropdown only changes the specs you see. It does not change the requests made with application credentials or app registration.
There are two exceptions when the underlying implementation should match the selected version:
- With Dev Portal app registration: If non-current versions have Route configurations that allow requests to specify the version in some way, each version must document how to modify the request to access the given version (for example, using a header).
- Without Dev Portal app registration: If the version can be accessed separately from other versions of the same API, each version must document how to modify the request to access the given version.
How does Konnect manage authentication and authorization on Gateway Services or control planes that are linked to my APIs?
When you link an API to a Gateway, you have two options:
- Link to a single Gateway Service with the Konnect Application Auth (KAA) plugin
- Link to a control plane with the Access Control Enforcement plugin
These plugins are responsible for applying authentication and authorization on the Gateway Service or control plane. The authentication strategy that you select for the API defines how clients authenticate.
The following table can help you decide which option to pick:
|
Option |
KAA plugin |
ACE plugin |
|---|---|---|
| Scope | Linked to a single Gateway Service | Linked to an entire control plane |
| Plugin applied… | Automatically on the Gateway Service linked to the API | Manually |
| Managed by… | Konnect. You can only modify it by configuring JSON in the advanced configuration for your application auth strategy. | You, by manually configuring the plugin. |
| Kong Gateway version | 3.6 or later | 3.13 or later |
| Can be used with declarative configuration | No, because the plugin is applied automatically | Yes, because you must configure the plugin |
| Can be used with API packages | No | Yes |
Do not configure the KAA and ACE plugins on the same control plane because their overlapping interactions can be unpredictable.