Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Flyte

Is there any information on requirements for internal `clientSecret` and corresponding `clientSecretHash` define <https://github.com/flyteorg/flyte/blob/5ab8cb887a5a7051070cb93fca603ed1f22f2f74/charts/flyte-binary/values.yaml#L124C4-L126|here> ? Or if there is a recommended way to generate these?

sorry <@UNR3C6Y4T> I also have the same question

I can help with docs/guide for this. Besides the comment in the chart, still unsure on what are accepted formats/options for those keys

i’d stick to normal characters, shouldn’t have new lines or anything in there

david has the bcrypt command documented if you need for the hash

<@U04RHGT28F2> that would be

```pip install bcrypt &amp;&amp; python -c 'import bcrypt; import base64; print(base64.b64encode(bcrypt.hashpw("&lt;your_client-secret&gt;".encode("utf-8"), bcrypt.gensalt(6))))'```

Thats great, thank you both - I will give that a shot :+1:

Sorry for the delay but :raised_hands: Auth is working for me now, however I am having issues with flytectl with OIDC… according to <https://docs.flyte.org/en/latest/deployment/configuration/auth_setup.html#:~:text=It%20should%20now,the%20next%20section.|the documentation> it should be picked up, but I’m getting a 464 response (apparently an AWS ALB <https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-troubleshooting.html#http-464-issues|custom response>) - I’m digging into it now, but is there any obvious thing I might be missing?

And <@U04H6UUE78B>, I’d be happy to make a PR to your `flyte-the-hard-way` repo with the auth setup if that would be helpful?

<@U04RHGT28F2> I'm glad you're moving closer. I will have a PR soon with instructions in the repo and will add you as reviewer if you don't mind

Regarding the 464 error, how's your ingress configured, or what's the output of

`kubectl get ingress -n &lt;your-namespace&gt;` ?

Untitled

Yep sounds good, thank you :+1:
This is the current configuration