I've followed https://github.com/unionai-oss/deploy-flyte/tree/main/environments/gcp/flyte-core and am working on adding authentication following the

flyte-core

section of https://docs.flyte.org/en/latest/deployment/configuration/auth_setup.html#apply-oidc-configuration authentication seems enabled, but when i load the initial page i see a CORS error in the network panel when calling https://accounts.google.com/o/oauth2/v2/auth?client_id=.... in particular, the payload has

*redirect_uri:* <https://localhost:30081/callback>

which seems like it maybe the problem, since i expect it to be

https://<your-deployment-URL>/callback

Sure thing! I'm looking through the available data to answer your question. Hold on a second... ⏳

@ancient-wolf-19325 how do i set this? in my

values-gcp-core.yaml

i have:

configmap:
  adminServer:
    server:
      httpPort: 8088
      grpcPort: 8089
      security:
        secure: false
        useAuth: true
        allowCors: true
        allowedOrigins:
          - "<my-deployment-URL>"
        allowedHeaders:
          - "Content-Type"
          - "flyte-authorization"
      auth:
        appAuth:
          thirdPartyConfig:
            flyteClient:
              clientId: flytectl
              redirectUri: <my-deployment-URL>/callback

i've also confirmed that my authorized redirect URI's are correct on the google side.

Ensure that the

redirectUri

in your

values-gcp-core.yaml

is correctly set to your deployment URL. Replace

<my-deployment-URL>/callback

with

https://<your-deployment-URL>/callback

. Also, verify that the

allowedOrigins

list includes your deployment URL without HTML encoding. If the issue persists, check the CORS settings in your Google OAuth client configuration to ensure they match the deployment URL. Would you like more detailed guidance on updating these configurations? Sources: - https://discuss.flyte.org/t/8579436/hi-community-i-tried-to-integrate-self-hosted-gitlab-as-an-e/ - https://github.com/flyteorg/flyte/issues/4955 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@ancient-wolf-19325 yes, i've done all that, i've just omitted the precise name for privacy

To resolve the CORS error, ensure the following steps are correctly implemented: 1. Update

redirectUri

: Ensure the

redirectUri

in your

values-gcp-core.yaml

is set to

https://<your-deployment-URL>/callback

without any HTML encoding. 2. Allowed Origins: In the

allowedOrigins

section, ensure your deployment URL is correctly specified and matches the domain from which requests are being made. 3. Google OAuth Configuration: Double-check that the authorized redirect URIs in your Google OAuth client settings exactly match the

redirectUri

specified in your Flyte configuration. 4. FlyteAdmin Config: According to Flyte documentation, ensure that the FlyteAdmin config allows CORS from the FlyteConsole domain. If these steps are correctly followed and the issue persists, consider checking network logs for any discrepancies in the request headers or additional CORS-related errors. Would you like more detailed guidance on any specific step? Sources: - Flyte Documentation - Flyte GitHub Issue 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.