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]: can't authenticate #99

Open
masterkain opened this issue Feb 27, 2025 · 1 comment · May be fixed by #101
Open

[Bug]: can't authenticate #99

masterkain opened this issue Feb 27, 2025 · 1 comment · May be fixed by #101
Assignees
Labels
bug Something isn't working
Milestone

Comments

@masterkain
Copy link

ChromaDB Version

0.4.x

Kubernetes Version

1.24.x

What happened?

if eq .Values.chromadb.auth.token.headerType "X_CHROMA_TOKEN"

are we sure this has to be this value? I think it should be X-Chroma-Token ? same goes for AUTHENTICATION

Environment details

k3s

Logs, Kubectl output, Manifests, etc.

@masterkain masterkain added the bug Something isn't working label Feb 27, 2025
@tazarov tazarov self-assigned this Feb 28, 2025
@tazarov tazarov added this to the 0.1.24 milestone Feb 28, 2025
@tazarov tazarov linked a pull request Feb 28, 2025 that will close this issue
@tazarov
Copy link
Contributor

tazarov commented Feb 28, 2025

@masterkain, thanks for raising this. Indeed the auth headers was broken and also the docs were misleading.

#101, should fix that by adding a helper function to parse and validate the value. Values should now also be case-insensitive and we should support X_CHROMA_TOKEN as well as X-Chroma-Token values for the headerType

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants