OAuth 2.0 (Client Credentials) authentication for our AdaptiveWork

Currently, REST API access supports only API Key authentication (a long-lived JWT passed via the Authorization: ApiKey <token> header). This presents two concerns:

Security — The API key is a static, long-lived token with no built-in expiry rotation mechanism. OAuth 2.0 client credentials flow provides short-lived access tokens that are automatically refreshed, reducing the risk of token compromise.

Integration compatibility — Several modern tools require OAuth 2.0 client credentials flow for service-to-service authentication and do not support static API key connections.

Would like to have OAuth 2.0 authentication (client credentials grant type) for AdaptiveWork. Specifically: A Token URL endpoint where we can exchange a client_id and client_secret for a short-lived access token and the ability to use that access token in the Authorization: Bearer <token> header for subsequent API calls.