Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Ensure OAuth credentials are fresh before using them in graph execution #8179

Open
Pwuts opened this issue Sep 25, 2024 — with Linear · 1 comment · May be fixed by #8191
Open

Ensure OAuth credentials are fresh before using them in graph execution #8179

Pwuts opened this issue Sep 25, 2024 — with Linear · 1 comment · May be fixed by #8191
Assignees
@Pwuts
Labels
platform/backend/executor

Comments

@Pwuts Linear
Copy link
Member

Pwuts commented Sep 25, 2024

The ExecutionManager fetches the needed credentials for a graph excution from Supabase, but it should also refresh them if needed using the appropriate OAuthHandler.
@Pwuts Pwuts self-assigned this Sep 26, 2024
@Pwuts Pwuts linked a pull request Sep 26, 2024 that will close this issue
Open
@Pwuts Linear
Copy link
Member Author

Pwuts commented Sep 26, 2024

This is made more complex by a few factors:

  • When a refresh token is used, the corresponding access token becomes invalid. So if one part of the system refreshes the token, this needs to be propagated to all other parts of the system.
  • Tokens refresh can (in principle) be initiated by both the executor and the rest_api server.

The only way I see to properly deal with this is to have centralized credentials management, and JIT retrieval of credentials for use.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Pwuts Pwuts

Labels
platform/backend/executor
Projects
None yet
Milestone
No milestone
1 participant
@Pwuts