krzysztof/landing_page
1
0
Fork 0
mirror of https://github.com/qdrant/landing_page.git synced 2026-10-06 03:18:30 +02:00
Code Issues Packages Projects Releases Wiki Activity

Add docs on Database API keys on Managed Cloud

Browse Source
This commit is contained in:
Sebastiaan van Steenis
2025-01-27 10:51:38 +01:00
parent f94f5a56cf
commit e2432123de
2 changed files with 35 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files
qdrant-landing/content/documentation/guides/security.md
+1 -1
View File
@@ -148,7 +148,7 @@ Both API keys can be used simultaneously.
*Available as of v1.9.0*
For more complex cases, Qdrant supports granular access control with [JSON Web Tokens (JWT)](https://jwt.io/).
This allows you to have tokens, which allow restricited access to a specific parts of the stored data and build [Role-based access control (RBAC)](https://en.wikipedia.org/wiki/Role-based_access_control) on top of that.
This allows you to create tokens which restrict access to data stored in your cluster, and build [Role-based access control (RBAC)](https://en.wikipedia.org/wiki/Role-based_access_control) on top of that.
In this way, you can define permissions for users and restrict access to sensitive endpoints.
To enable JWT-based authentication in your own Qdrant instance you need to specify the `api-key` and enable the `jwt_rbac` feature in the configuration: