chore: release v0.4.0

Author: dsferruzza

CHANGELOG.md

@@ -1,5 +1,17 @@
 # Changelog
 
+## v0.4.0
+
+- switch to Actix Web 4 (Actix Web 3 is no longer supported)
+- handle extraction and parsing of custom JWT claims
+- add a way to access parsed roles from handlers (every Keycloak role contained in the JWT)
+- add compatibility with the paperclip crate (under the `paperclip_compat` feature)
+- add passthrough policy setting to allow auth to be optional
+- add a `KeycloakAuth::default_with_pk()` helper function to initialize the middleware with default settings
+- improve extractors error types
+- expose a pure function to extract custom JWT claims from an Actix Web request
+- update to Rust 2021 edition
+
 ## v0.4.0-beta.2
 
 - support Actix Web 4.0.0-beta.10

Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "actix-web-middleware-keycloak-auth"
-version = "0.4.0-beta.2"
+version = "0.4.0"
 authors = ["David Sferruzza <[email protected]>"]
 edition = "2021"
 description = "A middleware for Actix Web that handles authentication with a JWT emitted by Keycloak"

README.md

@@ -11,10 +11,11 @@ A middleware for [Actix Web](https://actix.rs/) that handles authentication with
 ## Features
 
 - Actix Web middleware
-- deny HTTP requests that do not provide a valid JWT
+- deny HTTP requests that do not provide a valid JWT (or choose to allow them and handle the authentication state from a following middleware)
 - require one or several Keycloak realm or client roles to be included in the JWT
 - error HTTP responses sent from the middleware can have generic bodies as well as detailed error reasons
 - access JWT claims from handlers (for example: get the ID of the authenticated user)
+- parse custom JWT claims (using Serde)
 - access parsed roles from handlers (every Keycloak role contained in the JWT)
 - compatible with [paperclip](https://crates.io/crates/paperclip) using the `paperclip_compat` feature
 - store auth status in request-local data instead of returning a HTTP response (so that the next middleware/handler can try another auth mechanism, for example)