Hello! I am using Flyte-binary chate with GKE and I am trying to activate auth. Populated the values in chart but receving the following error in logs:

2023-07-30 12:52:23.957 PDT time="2023-07-30T19:52:23Z" level=info msg="Using config file: [/etc/flyte/config.d/000-core.yaml /etc/flyte/config.d/001-plugins.yaml /etc/flyte/config.d/002-database.yaml /etc/flyte/config.d/003-storage.yaml /etc/flyte/config.d/004 auth.yaml /etc/flyte/config.d/012-database-secrets.yaml /etc/flyte/config.d/014-auth-secrets.yaml]"
2023-07-30 12:52:24.411 PDT Error:
2023-07-30 12:52:24.411 PDT 1 error(s) decoding:
2023-07-30 12:52:24.411 PDT {}
2023-07-30 12:52:24.411 PDT * error decoding 'appAuth.selfAuthServer.staticClients[flytepropeller].client_secret': illegal base64 data at input byte 0
2023-07-30 12:52:24.415 PDT Usage:
2023-07-30 12:52:24.415 PDT flyte secret init [flags]
2023-07-30 12:52:24.415 PDT {}
2023-07-30 12:52:24.415 PDT Flags:
2023-07-30 12:52:24.415 PDT -h, --help help for init
2023-07-30 12:52:24.415 PDT -p, --localPath string Specifies where the secrets should be written.

@Haytham Amin, you need to compute the hash with bcrypt. https://discuss.flyte.org/t/9524105/hey-guys-trying-to-set-up-auth-with-the-flyte-binary-and-hav#82192706-ae7e-486b-b686-c0fb494ec465

Is this for all internal clientsecret entries or just the hashed one?

Yes! Please replace the value you generate with bcrypt in

clientSecretHash

.

I did that and still getting the same error! do I have to hash any other variable?

Can you give it a shot?

I did! I added the hashed secret in

clientSecretHash

and regular secret string in

internal.clientSecret

and still go the same error

Hey @David Espejo (he/him), any idea what might be the issue here?

@Haytham Amin are you planning on using Flyte's internal auth server? if so, you just need to hash the secret for

flytepropeller

. A new set of instructions was merged here: https://docs.flyte.org/en/latest/deployment/configuration/auth_setup.html#apply-oidc-configuration Please let us know if it answers your question

only if I need it

Yes, even using the external auth server, you still need the internal secret. Find here the relevant section: https://docs.flyte.org/en/latest/deployment/configuration/auth_setup.html#apply-external-auth-server-configuration

@David Espejo (he/him) how do I change the callback uri from http://flyte-flyte-binary:8088/callback to my domain ?

you need to specify your domain under

authorizedUris

yes

Ok! This worked. Now im trying to get flytecli to communicate with cluster. Why am I getting Not Found 404? Should I add

/console

to the endpoint?

cat ./flyteconfig.yaml
admin:
  endpoint: dns:///<PUBLIC_ACCESSABLE_DOMAIN>
  insecure: false
  insecureSkipVerify: true
  authType: ClientSecret
  clientId: flytepropeller
  clientSecretEnvVar: FLYTE_CLIENTSECRET
$ flytectl --config=flyteconfig.yaml version
{"json":{},"level":"warning","msg":"using insecureSkipVerify. Server's certificate chain and host name wont be verified. Caution : shouldn't be used for production usecases","ts":"2023-08-02T23:12:21Z"}
{
  "App": "flytectl",
  "Build": "145bc5c",
  "Version": "0.6.45",
  "BuildTime": "2023-08-02 23:12:21.162374874 +0000 UTC m=+0.037043299"
}
$ flytectl register files --config=flyteconfig.yaml --project=flytesnacks --domain=development --archive flyte-package.tgz --version=v1
{"json":{},"level":"warning","msg":"using insecureSkipVerify. Server's certificate chain and host name wont be verified. Caution : shouldn't be used for production usecases","ts":"2023-08-02T23:12:26Z"}
 --------------------------------------------------------------------------------------------------------------------- -------- --------------------------------------------------- 
| NAME                                                                                                                | STATUS | ADDITIONAL INFO                                   |
 --------------------------------------------------------------------------------------------------------------------- -------- --------------------------------------------------- 
| /tmp/register3175681439/0_example_project.house_price_prediction.house_price_predictor.generate_and_split_data_1.pb | Failed | Error registering file due to rpc error: code =   |
|                                                                                                                     |        | Unimplemented desc = unexpected HTTP status code  |
|                                                                                                                     |        | received from server: 404 (Not Found); transport: |
|                                                                                                                     |        | received unexpected content-type "text/plain;     |
|                                                                                                                     |        | charset=utf-8"                                    |
 --------------------------------------------------------------------------------------------------------------------- -------- --------------------------------------------------- 
1 rows
Error: rpc error: code = Unimplemented desc = unexpected HTTP status code received from server: 404 (Not Found); transport: received unexpected content-type "text/plain; charset=utf-8"
{"json":{},"level":"error","msg":"rpc error: code = Unimplemented desc = unexpected HTTP status code received from server: 404 (Not Found); transport: received unexpected content-type \"text/plain; charset=utf-8\"","ts":"2023-08-02T23:12:26Z"}

check your flyte/admin logs. i think maybe the data proxy service isn’t running correctly. best first check something simpler like flytectl get projects, see if that’s working