Skip to content
Projects

pac4j/http4s-pac4j has 42 GitHub stars and 15 forks. GitHot measured 0 stars in 24 hours. Last checked 2026-11-15 21:50 UTC. Last push 2026-11-14.

How these counts are measured

Measured star growth

in 24h
0
in 7 days
Update delayed
in 15 days
Update delayed
in 1 month
Update delayed

Net star changes over overlapping periods, not daily totals. Missing measurements are left blank. Stars measure attention, not software quality.

About

Security library for http4s

Security

README.md

Original

Maven Central Java 17+ Scala 2.12 | 2.13 | 3 http4s 0.23 Apache 2 license

http4s-pac4j is the http4s implementation of pac4j, the security engine for Java. If it is useful to you, please ⭐ star pac4j on GitHub: it helps other developers discover it!

The http4s-pac4j project is an easy and powerful security library for http4s web applications and web services which supports authentication and authorization, but also logout and advanced features like session fixation and CSRF protection. It's based on http4s 0.23 and on the pac4j security engine. The library is cross-built for Scala 2.12, 2.13 and 3. It's available under the Apache 2 license.

Main concepts and components:

  1. A client represents an authentication mechanism. It performs the login process and returns a user profile. An indirect client is for web application authentication while a direct client is for web services authentication:

▸ OpenID Connect - SAML - CAS - OAuth - HTTP - LDAP - SQL - JWT - MongoDB - Kerberos - IP address - REST API

  1. An authorizer is meant to check authorizations on the authenticated user profile(s) or on the current web context:

▸ Roles / permissions - Anonymous / remember-me / (fully) authenticated - Profile type, attribute - CORS - CSRF - Security headers - IP address, HTTP method

  1. The SecurityFilterMiddleware protects an url by checking that the user is authenticated and that the authorizations are valid, according to the clients and authorizers configuration. If the user is not authenticated, it performs authentication for direct clients or starts the login process for indirect clients

  2. The CallbackService finishes the login process for an indirect client

  3. The LogoutService logs out the user from the application and triggers the logout at the identity provider level.

Usage

  1. Add the required dependencies

  2. Define:

  1. Apply security

  2. Get the authenticated user profiles

Demo

The demo webapp for http4s-pac4j: http4s-pac4j-demo is available for tests and implements many authentication mechanisms: Facebook, Twitter, form, basic auth, CAS, SAML, OpenID Connect, JWT...

Versions

The latest released version is the Maven Central.

See the release notes.

See the migration guide as well.

Need help?

You can use the mailing lists or the commercial support.

Credits

Thanks to https://github.com/hgiddens/http4s-session for the Session implementation