#community-help

Issue with Accessing Metrics and Aliases in UI with RO Key

TLDR James faced a 401 error while accessing metrics and aliases with a Read-Only key. Kishore Nallan suggested using 'metrics.json:list' and 'aliases:list' actions to fix the issue; this solution worked.

22mo

Join the chat

Nov 12, 2021 (22 months ago)

Photo of md5-ae7223c767d7228418baf97773be94d6

James

08:56 PM

I'm creating a small read-only UI to view stats, collections, aliases, etc. As such I created a RO key with these parameters:

print(client.keys.create({
    "description": "Search and RO access key.",
    "actions": ["documents:search","metrics:get","aliases:get"],
    "collections": ["*"],
}))

The resultant key allows me to search across my collections, however, for metrics and aliases I'm getting a 401 with that key. Thought I scoped this correctly, but clearly I did not.

Nov 13, 2021 (22 months ago)

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

12:49 AM

Kishore Nallan ^

Photo of md5-4e872368b2b2668460205b409e95c2ea

Kishore Nallan

01:40 AM

Let me check on this and get back to you. What version of Typesense are you using?

James

03:56 AM

I'm on version 0.21.0

03:56

James

03:56 AM

Thanks!

Kishore Nallan

10:52 AM

James The actions must be metrics.json:list and aliases:list because those are listing end-points. Metrics requires .json suffix since we could support other formats in future.

To allow access to individual aliases (e.g. /aliases/foo), you need aliases:get permission.

James

04:50 PM

Got it. Thank you, I will make those changes.

Nov 16, 2021 (22 months ago)

James

06:57 PM

This worked, BTW. Thank you very much!

Nov 17, 2021 (22 months ago)

Kishore Nallan

01:56 AM

Welcome!

Typesense

Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI

Indexed 2764 threads (79% resolved)

Join Our Community Manage subscription

Similar Threads

Scoping API Key for All Permissions & Searches

James requests help to scope an API key for all searches and permissions. Jason suggests adding aliases:get and metrics:get. This suggestion doesn't resolve the issue; the thread is marked as unresolved.

24mo

Correct API Key Generation and Usage on Cloud

Tom faced 401 errors while creating keys via the Cloud API. Kishore Nallan clarified the correct syntax and mechanics, and identified a header mislabeling on Tom's part that caused the issue. They also discussed using scoped API keys.

11mo

Issue with API Key Format and Typesense API Calls

Adrian encountered a 401 error when making API calls using a key, and Jason helped correct the key's format. Adrian then created a Github issue about the problem.

1mo

API Key Permissions for Typesense Docsearch Scraper

JP asked about configuring API key actions for reindexing a site using Typesense. Kishore Nallan clarified the required permission. Then, JP and Jason discussed specific permission configurations, and JP made a documentation update to illustrate their findings.

8mo

Resolving Issues with Scoped API Keys in Typesense with Golang

Suvarna had problems with generating and using scoped API keys in Typesense with Golang. Several bugs misleading the user were found and fixed by Kishore Nallan.

158

24mo