4.3

4.3

HarperDB Docs
Getting Started
Developers
Administration
Deployments
Technical Details
- Reference
- Release Notes
  - HarperDB Tucker (Version 4)
    4.3.36
    4.3.35
    4.3.34
    4.3.33
    4.3.32
    4.3.31
    4.3.30
    4.3.29
    4.3.28
    4.3.27
    4.3.26
    4.3.25
    4.3.24
    4.3.23
    4.3.22
    4.3.21
    4.3.20
    4.3.19
    4.3.18
    4.3.17
    4.3.16
    4.3.15
    4.3.14
    4.3.13
    4.3.12
    4.3.11
    4.3.10
    4.3.9
    4.3.8
    4.3.7
    4.3.6
    4.3.5
    4.3.4
    4.3.3
    4.3.2
    4.3.1
    4.3.0
    4.2.8
    4.2.7
    4.2.6
    4.2.5
    4.2.4
    4.2.3
    4.2.2
    4.2.1
    4.2.0
    4.1.2
    4.1.1
    4.1.0
    4.0.7
    4.0.6
    4.0.5
    4.0.4
    4.0.3
    4.0.2
    4.0.1
    4.0.0
    HarperDB Monkey (Version 3)
    3.3.0
    3.2.1
    3.2.0
    3.1.5
    3.1.4
    3.1.3
    3.1.2
    3.1.1
    3.1.0
    3.0.0
    HarperDB Penny (Version 2)
    2.3.1
    2.3.0
    2.2.3
    2.2.2
    2.2.0
    2.1.1
    HarperDB Alby (Version 1)
    1.3.1
    1.3.0
    1.2.0
    1.1.0
More Help

Powered by GitBook

On this page

Developers

Security

PreviousCertificate Management NextJWT Authentication

Last updated 11 months ago

HarperDB uses role-based, attribute-level security to ensure that users can only gain access to the data they’re supposed to be able to access. Our granular permissions allow for unparalleled flexibility and control, and can actually lower the total cost of ownership compared to other database solutions, since you no longer have to replicate subsets of your data to isolate use cases.

JWT Authentication

Basic Authentication

mTLS Authentication

Users and Roles