New RunLLM response generated: >>>*# Question* Hi, I was curious if there is a way to add additional clients to the internal authorization server of flyte? At the moment I can interact with our flyte installation using e.g.

flytectl get workflows  -d development  -p flytesnacks --admin.authType ClientSecret --admin.clientId flytepropeller --admin.clientSecretLocation /Users/christoph/.flyte/secret --admin.endpoint dns:///....

where the file

/Users/christoph/.flyte/secret

contains the password I setup for

flytepropeller

. Is there a way to get additional

client_id

and

client_secret

values working? # Answer Yes, you can add additional clients to the internal authorization server of Flyte. This involves configuring the

values.yaml

file used during the Helm chart installation of Flyte. Specifically, you need to add the new client details under the

auth.selfAuthServer.staticClients

section. Here's an example configuration:

auth:
  enabled: true
  selfAuthServer:
    staticClients:
      flytepropeller:
        id: flytepropeller
        client_secret: <flytepropeller-secret>
        redirect_uris:
          - "http://localhost:3846/callback"
        grant_types:
          - refresh_token
          - client_credentials
        response_types:
          - token
        scopes:
          - all
          - offline
          - access_token
      new-client:
        id: new-client
        client_secret: <new-client-secret>
        redirect_uris:
          - "http://localhost:12345/callback"
        grant_types:
          - refresh_token
          - client_credentials
        response_types:
          - token
        scopes:
          - all
          - offline
          - access_token

After updating the

values.yaml

file, you need to upgrade your Helm release with the new configuration:

helm upgrade <release-name> flyteorg/flyte-core -n <your-namespace> --values <your-updated-values-file>.yaml

This will add the new client to the internal authorization server, allowing you to use the new

client_id

and

client_secret

for authentication. Sources: - Add support for leveraging pre-created secrets in flyte-binary helm chart - Update Auth docs Slack Link https://flyte-org.slack.com/archives/CP2HDHKE1/p1720105623.817169 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.