whenever you get a chance

does this path work for you guys? https://your.admin.url/config/v1/flyte_client and if so, could you tell me if the

authorization_metadata_key

is

flyte-authorization

if not, could you tell me if https://github.com/flyteorg/flytekit/blob/master/flytekit/configuration/creds.py#L42 that configuration option is set anywhere in your systems?

it shouldn’t be needed anymore (if auth is enabled, Admin has been publishing the metadata key that it expects for a while). just remembered that your auth flow did something out of band so wanted to confirm.

or @Dylan Wilder?

We’re probably good though

@Yee yes we instruct our users to set it in their configs for flyte-cli, but haven’t checked if it works without it

authorization_metadata_key=flyte-authorization

for flytectl we don’t actually, so I guess it works without it

does this path work for you guys? https://your.admin.url/config/v1/flyte_client

what do you mean by this?

But keep the rest of the url the same. And see if that page returns anything

If flytectl is working, it should.

And also check your.flyte.url/.well-known/oauth-authorization-server