Idea Summary
A current requirement of ours is to use an Azure AI Services OpenAI GPT-4 endpoint. However, an additional requirement is to use Azure AI Services API Management (APIM) in front of the endpoint. This requires OAuth2 authentication before sending the request with some additional headers: the API key, the user, and the application name. This is only possible currently by using a reverse-proxy because OAuth2 APEX Credentials are not able to be used with APEX Generative AI Services. Also, because the API key has to be hardcoded in the HTTP Headers field and there is no ability to use Substitution Strings for the user and the application name at the Workspace level in APEX. One of the big problems that we are running into is that when we use the AI for development assistance, there is no way to capture the user. We can work around this when the request is generated from an AI widget in an application by passing the user in the system prompt and replacing it in the headers, but there is no such option when the request is generated for development assistance.

Use Case
When using an Azure AI Services endpoint for an APEX Generative AI Service.

Preferred Solution (Optional)
Allow OAuth2 APEX Credentials to be used by APEX Generative AI Services and create a new substitution string (or something similar) feature for the Workspace level.