Support for OpenAPI 3.1.1 and later

[dubnemo]

Important

PLEASE DO NOT CREATE ISSUES RELATED TO MANAGED DEVELOPER PORTAL IN THIS REPOSITORY. Issues related to "Managed developer portal" will be closed automatically. Managed developer portal issues should be created directly in Azure Support + Troubleshooting in Azure portal. Contact Azure support (or) submit a post on Stack Overflow. Feature requests can be raised on the Azure Feedback Forum.

Every self-hosted developer bug report should have precise description and reproduction steps; console traces (or) source code references are appreciated.

Bug description

OpenAPI specifications are automatically translated to 3.0.1, losing a lot a of the new features in later versions of OAS especially the security features such as OAuth scopes.

Reproduction steps

Import of OAS yml translates to older JSON rendition, and Developer Portal does not have any feature definitions to work with.

Expected behavior

Version 3.2 will have more security features and V3.3 is slated to have more OIDC features including CIBA.
We need these feature to tighten down what endpoints truly has access to, and limit the visibility of these endpoints to only those the user is authorized to use. They should not even see these endpoints.
Developer Portal will be able to filter

Is self-hosted portal?

Yes / No

Warning

"Managed developer portal issues" will be closed automatically. See above for more details.

Release tag or commit SHA (if using self-hosted version)

[e.g., release 2.0.0, commit c45da9778b70d369aba60fa2e63c191efe2b548f]

API Management service name

[e.g., contoso-api]

Environment

• Operating system: [e.g., iOS]
• Browser: [e.g., Google Chrome, Safari]
• Version: [e.g., 22]

Additional context

Add any other context about the problem here, including screenshots.

[dubnemo]

Is there any update on upgrading APIM to leverage OAS LTS?

[gmli]

Today, if you create a minimal endpoint (a single nullable string in a json) in Dotnet 10 the resulting OpenAPI 3.1 file (which is valid !) is refused by the Azure APIM.
OpenAPI 3.1 is the default for Dotnet 10.

EDIT : sorry @dubnemo I meant 3.1.1

[dubnemo]

Today, if you create a minimal endpoint (a single nullable string in a json) in Dotnet 10 the resulting OpenAPI 3.1 file (which is valid !) is refused by the Azure APIM. OpenAPI 3.1 is the default for Dotnet 10.

It seems the right hand is not aware of what the left hand is working on.
OAS 3.1.1 should ideally be the default, as 3.1 has a bug.