Bug: GATEWAY_SHOULDIMPERSONATE & INTROSPECTION_AUTHENTICATION seems to be ignored in multi-cluster setup

[n3rdc4ptn]

In the new multi-cluster setup #240 the gateway ignores the env variables and uses the specified token from the ClusterAccess resource for all requests. We expect it to just use the token for the CRD fetching and uses the authorization specified in the request to authenticate against the remote cluster.

env configuration i use:

export ENABLE_KCP="false"
export MULTICLUSTER="true"

export GATEWAY_USERNAMECLAIM="sub"
export GATEWAY_SHOULDIMPERSONATE="false"

export GATEWAY_CORS_ENABLED="true"

export AUTHENTICATE_SCHEMA_REQUESTS="true"
export INTROSPECTION_AUTHENTICATION="true"

export LOCAL_DEVELOPMENT="false"

Details

When using an invalid token, the gateway also logs:

{"level":"error","service":"crdGateway","error":"token is malformed: token contains an invalid number of segments","time":"2025-07-02T10:39:16+02:00","caller":"REDACTED","message":"Failed to parse token"}

Similar issue as before: #200

[vertex451]

Schema fetching with invalid token is fixed, switching to token bug

[vertex451]

fixed in #274