Release Notes

(Strapi) Now available: developer authentication using Microsoft EntraID.

(Strapi) Fixed an issue with access permissions to Guides.

(Strapi) You now have the option to control access to the Guides screen in your portal. Select the Roles that can access it.
You can assign roles to developers in API DOCS  SETTINGS & PERMISSIONS.

(Strapi) We added a screen to notify that the page is restricted when the developer does not have access to the API catalog, API Status, and Apps.

(Strapi) Fixed the issue that caused an "incorrect username or password" error message when trying to log in after a user’s role was deleted and replaced with a default role.

(Strapi) Duplicate APIs were being displayed on the App creation screen when AWS APIs were associated with roles.

(Strapi) Fixed the SAVE button, which would become disabled after creating or deleting a role.

(Strapi) The Products screen was breaking when editing a product that did not exist in Strapi.

(Strapi) Introduced the concept of roles. You can now manage access to your portal by defining roles for developers/users.

We added the secure attribute to portal cookies.

(Strapi) We created a new screen for your Developer Portal: API Status. Consumers of your APIs can now check resource availability details for the APIs.

Fixes implemented in the Developer Portal Strapi:

Created the "Developers" tab in Settings. The auto-approval setting for developer registrations is now in this tab.

Revised the ReCaptcha component in the password reset and developer registration confirmation forms.

Fixed the issue with API names containing special characters.

Implemented necessary adjustments for compatibility with Sensedia API Manager version 5.

Adjusted the rule for API deletion. It is now only possible to delete APIs that were manually imported. APIs imported automatically and non-native ones cannot be deleted individually.

Resolved an issue when attempting to import a custom provider.

Fixed a problem when re-importing an API from a non-native connection.

AWS Apps listing now only returns native connections.

You can now send additional information (e.g., tokens) along with AWS app credentials.

Added a new element to the AWS App creation and approval flow: the AWS API Key ID field.

Fixed an issue that caused an error when removing apps from an AWS API without plans.

Fixed an issue that resulted in an error when changing credentials while approving an AWS app modification.

You can now manage AWS Apps, approving or rejecting new registrations.

Created the Consumers > Apps page, dedicated to AWS gateway Apps.