Crate kvarn_auth

source ·
Expand description


A fast, simple, and customizable authentication extension for use in Kvarn. It’s impossible to shot yourself in your foot!

Provides an easy-to-use JWT-based authentication helper with support for persistent logins and validation servers.

You provide an async callback which gives the user a level of authorization. You can return any structured data based on serde. The JWT is automatically renewed, as the server stores a credentials cookie (encrypted using the server’s private key). Everything is configurable.

⚠️ Warning: This crate has not been audited. All dependencies I use have. Use at your own risk.

I do however personally use this for production systems.

§Front-end usage

A small JS library is provided for logging in and out and to get the current status of the user. See it and it’s docs for more details.

§Validation servers

An important feature of this library is validation servers. This enables a deployment of kvarn-auth to multiple different physical servers, without sharing the private key which can sign anybody in. This is achieved by using fast asymmetric cryptography. See ecdsa_sk for more info.

§Persistent logins

Along with the usual JWT cookie, kvarn-auth sends a credentials cookie. It contains the user’s credentials encrypted using the secret/private key of the server. This allows for automatic renewal (using Kvarn’s excellent extension system) when the JWT has expired. The credentials cookie is encrypted to avoid XSS attacks stealing the user’s password, which the user probably reused on other websites; this is an effort to help users.

You can enable Builder::with_force_relog_on_ip_change to make any cookie stealing useless. We embed the user’s IP in the JWT and credentials and only allow them if the IP is the same. This may be annoying for the users (especially if your user-base is predominantly on mobile), but greatly decreases the risk of account theft. So probably use it for banking :)


  • 0.1.x - kvarn v0.5
  • 0.2.x - kvarn v0.6


// please use a strong random secret (>1024bits of entropy to be safe)
let secret = b"this secret protects all the JWTs and the credentials".to_vec();
let mut accounts: HashMap<String, String> = HashMap::new();
accounts.insert("icelk".into(), "password".into());
let auth_config = kvarn_auth::Builder::new()
    // the authentication's scope is limited to routes starting with `/demo/`.
    // according to Kvarn's internal redirects, `/demo/login.` is shorthand for `/demo/login.html`
    .build::<(), _, _>(
        move |user, password, _addr, _req| {
            let v = if accounts.get(user).map_or(false, |pass| pass == password) {
            } else {
        kvarn_auth::CryptoAlgo::EcdsaP256 { secret },

let mut extensions = kvarn::Extensions::new();

auth_config.mount(&mut extensions);
let login_status = auth_config.login_status();

    move |login_status: kvarn_auth::LoginStatusClosure<()>| {
        let auth_data =
            if let kvarn_auth::Validation::Authorized(ad) =
                login_status(req, addr)
        } else {
            return default_error_response(
                Some("log in at `/demo/login.html`"),
        // continue with your API, with a guarantee



  • integrationsintegration-fs
    Integrations with databases to get started more quickly.


  • You can use multiple authentication setups on a single site, but make sure that the respective Builder::with_cookie_paths do not overlap. You MUST set with_cookie_path to use more than 1 auth setup.
  • The configured authentication. This can be attached to a Kvarn host using the Self::mount method. You can call Self::login_status to get a function to use in your extensions to check for authentication status.


  • The data in the JWT.
  • The cryptographic algorithm to use to ensure the authenticity of the data.
  • The state of the user in question.
  • ValidationAlgorsa or ecdsa
    The algorithm used when running in validation mode.


  • Get the signing key for secret.

Type Aliases§