You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Confirm this is a feature request for the Node library and not the underlying OpenAI API.
This is a feature request for the Node library
Describe the feature or improvement you're requesting
Currently, Azure OpenAI authentication only supports using azureADTokenProvider, but not azureADToken itself.
But some enterprise customers may manage AD token generation in a separate process.
This requires openai-node SDK to supports providing azureADToken directly, as in the Python SDK (link)
Such support will also benefit the uptake of recently released Codex CLI (which uses openai-node SDK under the hood). See ongoing issues/PR there (#11, #92)
Additional context
No response
The text was updated successfully, but these errors were encountered:
Plain old tokens are a legacy idea since they expire. Python supported tokens at first and then introduced a concept of Providers to help with expiration; keeping direct token use as legacy support.
JS came afterwards and has learned from Python mistakes -- no need for raw tokens; providers can do the same and more.
Someone who wants to manage their own tokens ought to do that by creating their own provider. For example:
Confirm this is a feature request for the Node library and not the underlying OpenAI API.
Describe the feature or improvement you're requesting
Currently, Azure OpenAI authentication only supports using azureADTokenProvider, but not azureADToken itself.
But some enterprise customers may manage AD token generation in a separate process.
This requires openai-node SDK to supports providing azureADToken directly, as in the Python SDK (link)
Such support will also benefit the uptake of recently released Codex CLI (which uses openai-node SDK under the hood). See ongoing issues/PR there (#11, #92)
Additional context
No response
The text was updated successfully, but these errors were encountered: