Context
Today the SDK owns authentication: when a task has an auth policy, it builds the AuthProvider and performs the OAuth2/OIDC token exchange itself.
When running inside a framework (Quarkus) that already manages identity, the framework should be able to take over and produce the Authorization value, suppressing the SDK's own token exchange.
Proposal
Make AuthProviderFactory pluggable so a custom implementation can be provided, with the current behavior as the default when none custom AuthProviderFactory is registered.
Context
Today the SDK owns authentication: when a task has an auth policy, it builds the AuthProvider and performs the OAuth2/OIDC token exchange itself.
When running inside a framework (Quarkus) that already manages identity, the framework should be able to take over and produce the Authorization value, suppressing the SDK's own token exchange.
Proposal
Make AuthProviderFactory pluggable so a custom implementation can be provided, with the current behavior as the default when none custom
AuthProviderFactoryis registered.