cuddly-jelly-27016
08/25/2025, 12:10 AMauth:
appAuth:
thirdPartyConfig:
flyteClient:
clientId: flytectl
redirectUri: <http://localhost:53593/callback>
scopes:
- offline
- all
selfAuthServer:
staticClients:
flyte-cli:
id: flyte-cli
redirect_uris:
- <http://localhost:53593/callback>
- <http://localhost:12345/callback>
grant_types:
- refresh_token
- authorization_code
response_types:
- code
- token
scopes:
- all
- offline
- access_token
public: true
flytectl:
id: flytectl
redirect_uris:
- <http://localhost:53593/callback>
- <http://localhost:12345/callback>
grant_types:
- refresh_token
- authorization_code
response_types:
- code
- token
scopes:
- all
- offline
- access_token
public: true
flytepropeller:
id: flytepropeller
client_secret: "${secret}"
redirect_uris:
- <http://localhost:3846/callback>
grant_types:
- refresh_token
- client_credentials
response_types:
- token
scopes:
- all
- offline
- access_token
public: false
### Expected behavior
Ideally the token would refresh in the background logins would not be necessary after the initial login
### Additional context to reproduce
This is hosted in GCP, using Google Identity for authentication
### Screenshots
No response
### Are you sure this issue hasn't been raised already?
• Yes
### Have you read the Code of Conduct?
• Yes
flyteorg/flytecuddly-jelly-27016
08/25/2025, 12:10 AM