#2959 [Core feature] Add Audience parameter in ClientSecret Authentication flow. Issue created by shahwar9 Motivation: Why do you think this is important? We are deploying Flyte as its ML Workflow orchestrator. Auth0 server expects that authentication flow uses

Audience

in its handshake process. When using Flyte with Authentication enabled, Flyte Scheduler and Flyte Propeller talk to Auth0 server with ClientSecret flow. Having no option to set Audience parameter in ClientSecret flow has halted our deployment as we are not able to use Flyte with Authentication. Read more in Audience: https://auth0.com/docs/secure/tokens/access-tokens/get-management-api-access-tokens-for-production#get-access-tokens The reason this is important is it expands the use case of Flyte with users taking extra precaution by using Audience. It does not change anything for the users who do not want to use Audience, so it is a non-breaking change to make. Goal: What should the final outcome look like, ideally? Flytepropeller, Flyte Scheduler and any other backend service that uses ClientSecret flow for authentication should have the option to enable Audience via values.yaml configs. An example for setting Audience within config is already present at Flyteadmin config: flyte/charts/flyte-core/values-keycloak-idp-flyteclients-without-browser.yaml Line 527 in </flyteorg/flyte/commit/01f7cd5c5fa7b713062fc8338821a956422639ba|01f7cd5> Describe alternatives you've considered I am not sure of an alternative solution in this case, the company policies are pretty tight to use Audience in every Authentication flow. Propose: Link/Inline OR Additional context Since ClientSecret flow is using Auth2 golang SDK so I dug a little bit into it and probably something that can help Flyte implement is this: golang/oauth2@01b79d9 Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte