AscendingCreations / AxumSession

Axum Session 📑 Overview provide's a Session management middleware that stores all session data within a MemoryStore internally. Optionally it can save data to a persistent database for long term storage. Uses Cookie or Header stored UUID's to sync back to the session store. • Cookies or Header Store of Generated Session UUID and a Store Boolean. • Uses a DatabasePool Trait so you can implement your own Sub Storage Layer. • Convenient API for no need to mark as Read or Write making Usage Easier. • Uses for internal memory lookup and storage to achieve high throughput. • Uses Serde for Data Serialization so it can store any Serde supported types into the Sessions data. • Supports Redis, SurrealDB, MongoDB and SQLx optional Databases out of the Box. • Supports Memory Only usage. No need to use a persistent database. • Supports Cookie and Header Signing for integrity, and authenticity. • Supports Database Session Data Encryption for confidentiality, integrity. • Supports SessionID renewal for enhanced Security. • Optional Fastbloom key storage for reduced Database lookups during new UUID generation. Boosting Bandwidth. • Optional Rest Mode that Disables Cookies and uses the Header values instead. • uses to ensure everything is implemented as safe rust. • has an API to allow further control of a session. • uses IP address's and user agent to deter spoofing of signed cookies and headers. 🚨 Help If you need help with this library or have suggestions please go to our Discord Group 📦 Install Axum Session uses [ ]. to your cargo include for Axum Session. [ ]: https://github.com/tokio-rs/tokio 📱 Cargo Feature Flags | Features | Description | | ----------------------------- | -------------------------------------------------------------------------------------------------- | | | Enables functions that provide more control over sessions. | | | Disables cookie handling and instead only uses a header. For rest API requests and responses. | | | Enables optional in-process key storage. This increases RAM usage depending on Fastbloom settings. | | Database Crate | Persistent | Description | | ----------------------------------------------------------------------------------- | ---------- | ----------------------------------------------------------- | | | Yes | Sqlx session store | | | Yes | Surreal session store | | | Yes | Mongo session store | | | Yes | RedisPool session store | 🔎 Example Default Setup You can find examples within the 🔑 Key Store Details To enable and use fastbloom key storage for less database lookups. Add the feature to the crate’s features. This feature will increase the ram usage server side. but will heavily improve the bandwidth limitations and reduce latency of returns from the server. This is based on how much the and are set too. The higher they are the more ram is used. You will also need to Enable the bloom filter in the config for it to be used. By default, the is enabled and these config options exist whither or not the feature is enabled. Please refer to and within the documents to set the options. Otherwise stick with the default settings which should work in most situations. Just do note these options provide on how many False positives could possibly occur when comparing a UUID to what currently exists, which means it will keep trying till it finds none that match. Higher values decrease the chance of a false positive but increase ram usage. 😎 Session Login and Authentication via For user login, login caching and authentication please see .