omnium

A set of extensions for building web applications on axum.

Unstable: This crate is not ready for use. The author is building out these extensions to iterate on a proof of concept, and the surface may change frequently.

api

The api::responses module provides a set of response conventions for axum handlers, implementing axum's IntoResponse trait for typical use cases.

A handler returns responses::Result, which represents HTTP responses on the Ok(...) arm regardless of status code:

// ...
use omnium::api::responses::{Result, Response};

async fn handler() -> Result {
    let result = try_do_or_err().await;
    match result {
        Ok => Response.status(StatusCode::ACCEPTED).into()
        Err => Response.status(StatusCode::CONFLICT).into()
    }
}

Response conventions are provided through the responses::Response struct. The handler result type responses::Result implements From<responses::Response>, so responses::Response can be returned from a handler with a call to .into().

A handler can return a JSON response for any serializable body, with a default OK status:

async fn handler() -> Result {
    Response.json(body).with_status(StatusCode::IM_A_TEAPOT).into()
}

A handler can return a simple status response, implicitly deriving a response body as appropriate for the status:

async fn handler() -> Result {
    Response.status(StatusCode::OK).into()
}

An additional detail message can be added to the status response body:

async fn handler() -> Result {
    Response.status(StatusCode::OK).with_detail("Additional detail".into()).into()
}

Finally, the Err arm is used to handle internal server errors. A handler can return Into<anyhow::Error>, which will be rendered as an INTERNAL_SERVER_ERROR response:

async fn handler() -> Result {
    let success = try_do_or_err().await?;
    // ...
}

This error handling convention is provided by an implementation of IntoResponse for Into<anyhow::Error>, added by this crate. With this convention, unhandled errors have built-in IntoResponse rendering and other errors must be rendered explicitly by a handler.

security

The security module provides JWT-based authentication middleware, with utilities for a cookie-based credential exchange or the authorization header for browser-based or programmatic authentication.

Create a service secret:

let service_secret = create_service_secret();

Configure authentication middleware:

#[derive(Clone)]
struct AppUser {}

struct ExampleSessionState {
    pub service_secret: ServiceSecret,
}

impl SessionState<AppUser> for Arc<ExampleSessionState> {
    async fn service_secret(&self) -> anyhow::Result<&ServiceSecret> {
        // Return secret from application secret manager:
        Ok(&self.service_secret)
    }


    async fn user_lookup(&self, _user_id: String) -> anyhow::Result<Option<AppUser>> {
        // Return user from application: database:
        Ok(Some(AppUser {}))
    }

    fn extract_credential(&self, request: &Request, _cookies: &CookieJar) -> Option<Credential> {
        Credential::from_authorization_header(&request)
    }
}

Attach authentication middleware:

fn app(state: Arc<ExampleSessionState>) -> Router {
    Router::new()
        .route("/api/user", get(|| async { "Hello, user!" }))
        .layer(from_fn_with_state(
            state.clone(),
            authenticate::<AppUser, Arc<ExampleSessionState>>,
        ))
        .with_state(state)
}

Create the user session:

create_session(
    "some-user-id",
    &EncodingKey::from_secret(state.service_secret.value.as_bytes()),
    Duration::from_secs(60),
);

With Credential::from_authorization_header, a client may pass the session as the authorization header. With Credential::from_cookie, a client may pass the session as the __Host-omn-sess cookie. For a simple, user-facing web application, you can set the __Host-omn-sess cookie when the user signs in, in order to authenticate requests to the service running on the same origin. If the application shares a session across multiple services on different origins, it can expose the session for use by the client in the authorization header for programmatic, cross-origin requests. You can plug in your own handling for extracting credentials from requests with a custom extract_credential handler.

Requests from an unauthenticated user will reject with a 401 response.

For an authenticated user, the user object from user_lookup can be retrieved from request state to avoid redundant lookup in handlers:

pub async fn handler(
    Extension(caller): Extension<AppUser>,
) {
    println!("Caller is: {}", caller);
}

Because a variety of data may need to be passed and verified between an application and its users, encode_claims and decode_claims may also be used for other purposes other than authentication. Note that claims are signed but not encrypted.

In addition to claims-based utilities, this crate wraps aes_gcm to provide utilties encrypt_string_aes256_gcm and decrypt_string_aes256_gcm. A secret created by create_service_secret can also be used with these encryption utilities.