Fresh plugin installation fails with 401 - a valid `x-typesense-api-key` header must be sent. about firestore-typesense-search HOT 6 CLOSED

It either has to be a full verbatim match, or a regex. So if you intend for that API key to allow access to all collections that start with jsancho_ you want to set it up as jsanco_.* in the API key collections key

Yikes! that was pretty daft of me.

I'll create some new keys and reconfigure the function.
I would have sworn that's the key I used to initially populate the collection, but I must have used on of the auto-generated ones at the beginning.

thanks! 🙏🏻

from firestore-typesense-search.

here's the full stack trace in case this helps

from firestore-typesense-search.

Could you make sure that you're using your Typesense Admin API key (and not your search-only api key) when configuring the extension?

You can verify your API keys' permissions by going to the API Keys section in your Typesense Cloud cluster dashboard (on the right side pane at the bottom).

from firestore-typesense-search.

Could you make sure that you're using your Typesense Admin API key (and not your search-only api key) when configuring the extension?

You can verify your API keys' permissions by going to the API Keys section in your Typesense Cloud cluster dashboard (on the right side pane at the bottom).

Yes, the key is one with access to all actions but a restricted set of collections.

I have actually used that key to populate the collections initially from a local node project, so it should be fine.

from firestore-typesense-search.

Looks like the collections permission is configured incorrectly in Typesense Cloud.

It either has to be a full verbatim match, or a regex. So if you intend for that API key to allow access to all collections that start with jsancho_ you want to set it up as jsanco_.* in the API key collections key

from firestore-typesense-search.

Happy to help!

from firestore-typesense-search.