#community-help

Authorization Issues and Version Update Queries

TLDR gab was having authorization issues with multisearch but Jason advised using the collection name instead of the alias when creating the key. gab also queried about updating the cloud cluster to a later version.

30mo

Join the chat

Jul 30, 2021 (30 months ago)

Photo of md5-8be2a24edf7a95c9c74abce4b1130c3e

gab

05:25 PM

Hi,
I have the following case where I'm not authorized. Cannot find why:
Key that exist

{
      "actions": [
        "documents:search"
      ],
      "collections": [
        "products",
        "wharehouses"
      ],
      "value_prefix": "fKzc"
    }

Aliases that exists

{
  "aliases": [
    {
      "collection_name": "prod-wharehouses-21-07-30-14",
      "name": "wharehouses"
    },
    {
      "collection_name": "prod-products-21-07-30-16",
      "name": "products"
    }
  ]
}

Collections that exists

[
{ "name": "prod-wharehouses-21-07-30-14"},
{ "name": "prod-products-21-07-30-16"}
]

I'm trying using the first key to search (multisearch) but I'm not authorized.
The same happen if I try to export documents

GET /collections/products/documents/export

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

05:33 PM

gab you want to use the collection name, not the alias name when creating the key

05:35

Jason

05:35 PM

IIRC, you can even add regex collection names when creating the key… We spoke about, I need to look deeper to see if it made it into a release.

gab

05:38 PM

Ok after looking deeper it looks like I'm assigning wrong permission. I Should have assigned documents:export /documents:get . It seems to work with the alias. I'm curious for the regexp because I do not know the collection names.

I will check if for multi search I need something like documents:multisearch instead of documents:search

05:46

gab

05:46 PM

~~It doesn't works for searching permissions. Strange~~
it works fine with an alias with documents:search

05:50

gab

05:50 PM

I have the version

{
  "state": 1,
  "version": "0.21.0.rc24"
}

Is it possible to migrate my cloud cluster to 0.21 ?
Is there a way so I can update it myself for later version updates?

Jason

06:35 PM

Oh good to know it works with an alias! Wasn't anticipating that use case 🙂

06:38

Jason

06:38 PM

gab Confirming that we did release support for regex collection names: https://github.com/typesense/typesense/issues/139

Typesense

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

Indexed 3015 threads (79% resolved)

Join Our Community

Similar Threads

Using Aliases in Typesense Search Queries

Babin had a question about using aliases in Typesense search queries, specifically when passing collection names. Jason helped identify a misconfiguration and provided guidance, resolving the issue.

9mo

Fixing Corrupted Documents and Upgrading Typesense Cloud Version

gab had issues with corrupted documents in Typesense Cloud. Jason suggested upgrading to version 0.24.1.rc, which resolved the issue. They also discussed CORS domain management.

9mo

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.

11mo

Cold Start Problem with Dynamic Collections

Adrian reported cold start issues with dynamic collections. Jason suggested using wildcard `*` for query_by parameters, upgrading to `0.25.0.rc34`, and clarified conventions. Adrian's issues were resolved but they reported a limitation that will potentially be addressed.

6mo

Resolving Issues with Infix and Prefix in Query Searches

Daren struggled with searches missing values in production. Jason and Kishore Nallan offered insights and created new features to help solve the problem, which was then tested and deployed by Daren.

5mo