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.

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

[Bug] Missing Client Authentication as a result of the new User Authentication #653

Open
moritzzingg-netlight opened this issue Mar 6, 2025 · 0 comments · May be fixed by #656
Open

[Bug] Missing Client Authentication as a result of the new User Authentication #653

moritzzingg-netlight opened this issue Mar 6, 2025 · 0 comments · May be fixed by #656
Milestone

Comments

@moritzzingg-netlight
Copy link
Contributor

The switch from the simple hard-coded token-based authentication to a github user authentication (#539) broke the client authentication necessary for garbo to push data into the DB via the API.

Fix:

  • Create an additional client authentication endpoint /auth/github to allow client authentication
  • Client provides a secret instead of a github code to get an API token
  • Implement routine into garbo pipeline to first request API token using secret before making proper API requests
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In progress
Development

Successfully merging a pull request may close this issue.

1 participant