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

Points Scrolling is rejected with 403 when using Read-Only API Key #158

Closed
kemkemG0 opened this issue Feb 6, 2024 · 2 comments
Closed

Comments

@kemkemG0
Copy link

kemkemG0 commented Feb 6, 2024

Current Behavior

Steps to Reproduce

  1. Set a read-only api key.
  2. Go to /dashboard and try clicking any collection.
  3. You should get the error like the picture.
Screenshot 2024-02-05 at 11 56 07 PM
  1. or you can reproduce this from the console by querying like this
POST /collections/{name}/points/scroll
{}

Expected Behavior

We can explore the vectors and payloads from the UI and we can query POST /collections/{name}/points/scroll from console UI

Possible Solution

Context (Environment)

Detailed Description

Post on discord
https://discord.com/channels/907569970500743200/1204337568431341608/1204337568431341608

Possible Implementation

@kemkemG0 kemkemG0 changed the title Points Scrolling is rejected with 403 when using Read-Only API Key #3542 Points Scrolling is rejected with 403 when using Read-Only API Key Feb 6, 2024
@timvisee
Copy link
Member

timvisee commented Feb 6, 2024

Thank you for your report! I've quickly identified the problem and am picking this up now.

@timvisee
Copy link
Member

timvisee commented Feb 6, 2024

I've fixed this issue in qdrant/qdrant#3544. Once it's merged, it'll be part of our next release.

Thank you for reporting this!

Closing this now, since I opened an issue for the core problem here: qdrant/qdrant#3543, qdrant/qdrant#3544

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants