Which feature is supported by the Okta org authorization server but not by the Okta custom Authorization server?

The choice regarding minting Access Tokens with Okta API Scopes is supported by the Okta org authorization server because it is designed to work seamlessly with OAuth 2.0 and OpenID Connect standards, which include the use of API scopes for defining the permissions associated with Access Tokens. This feature allows organizations to have fine-grained access control over the resources they protect with the tokens.

The Okta org authorization server is the default server that comes pre-configured with the necessary features for developers and enterprises looking to implement an identity and access management solution quickly and efficiently. It is fully integrated with Okta’s capabilities to handle API tokens and negotiate scopes that correspond to various actions or data sets across APIs.

In contrast, while custom authorization servers offer flexibility and the ability to tailor authorization flows and implementations, they focus more on customized and specific use cases in a way that might not include the standardized minting of Access Tokens with API Scopes as the primary implementation.

It is important to recognize how each feature aligns with the intended usage of the service being discussed. The org authorization server prioritizes ease of use and compliance with standard practices, making it the appropriate choice for minting Access Tokens in a way that adheres to established protocols.