<#1876 Feat: Add Audience + Scopes Param to PKCE a...
# flyte-github
a
#1876 Feat: Add Audience + Scopes Param to PKCE and DeviceCode Auth Flows Pull request opened by PudgyPigeon TL;DR This PR adds the
audience
parameter into the PKCE/AuthorizationClient and DeviceCodeAuthenticator auth flows. This param is derived from
auth_helper.RemoteClientConfigStore.get_client_config()
Also, the
scopes
configuration - derived from
config.yaml
by way of
configuration.PlatformConfig
is now exposed to the aforementioned auth flows. Changes are also made to the way the scopes parameter is parsed in the
token_client
module to bring it in line with the AuthorizationClient class flow. This now makes it so that Auth0 can use the PKCE and DeviceCode Auth flows without errors. Caching + refresh tokens is not included in this PR but a new one can be made shortly. Type ☑︎ Bug Fix ☑︎ Feature ☐ Plugin Are all requirements met? • [x ] Code completed ☐ Smoke tested ☐ Unit tests added • [x ] Code documentation added ☐ Any pending items have an associated Issue Complete description This PR adds the
audience
parameter into the PKCE/AuthorizationClient and DeviceCodeAuthenticator auth flows. This param is derived from
auth_helper.RemoteClientConfigStore.get_client_config()
Also, the
scopes
configuration - derived from
config.yaml
by way of
configuration.PlatformConfig
is now exposed to the aforementioned auth flows. Changes are also made to the way the scopes parameter is parsed in the
token_client
module to bring it in line with the AuthorizationClient class flow. This now makes it so that Auth0 can use the PKCE and DeviceCode Auth flows without errors. Caching + refresh tokens is not included in this PR but a new one can be made shortly. Tracking Issue https://github.com/flyteorg/flyte/issues/ Follow-up issue NA OR https://github.com/flyteorg/flyte/issues/ flyteorg/flytekit Codecov: 54.62% (-0.01%) compared to 42f2324 Codecov: 10.00% of diff hit (target 54.63%) ✅ 28 other checks have passed 28/30 successful checks