The jee-pac4j project is an easy and powerful security library for JEE 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 the pac4j security engine. It's available under the Apache 2 license.
| jee-pac4j | Module for JavaEE webapp | Module for JakartaEE webapp | JDK | pac4j | Usage of Lombok | Status |
|---|---|---|---|---|---|---|
| version >= 8 | javaee-pac4j | jakartaee-pac4j | 17 | v6 | Yes | In development |
| version >= 7 | javaee-pac4j | jakartaee-pac4j | 11 | v5 | No | Production ready |
| version >= 6 | jee-pac4j | 11 | v5 | No | Production ready | |
| version >= 5 | jee-pac4j | 8 | v4 | No | Production ready |
- A client represents an authentication mechanism. It performs the login process and returns a user profile. An indirect client is for web applications authentication while a direct client is for web services authentication:
▸ OAuth - SAML - CAS - OpenID Connect - HTTP - Google App Engine - Kerberos - LDAP - SQL - JWT - MongoDB - CouchDB - IP address - REST API
- An authorizer is meant to check authorizations on the authenticated user profile(s) or on the current web context:
▸ Roles - Anonymous / remember-me / (fully) authenticated - Profile type, attribute - CORS - CSRF - Security headers - IP address, HTTP method
-
A matcher defines whether the
SecurityFiltermust be applied and can be used for additional web processing -
The
SecurityFilterprotects 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 -
The
CallbackFilterfinishes the login process for an indirect client -
The
LogoutFilterlogs out the user from the application and triggers the logout at the identity provider level -
The
JEEContextand theProfileManagercomponents can be injected -
The
FilterHelperhandles the filters and their related mappings.
- the security configuration
- the callback configuration, only for web applications
- the logout configuration
Two demo webapps: jee-pac4j-demo (a simple JSP/servlets demo) and jee-pac4j-cdi-demo (a more advanced demo using JSF and CDI) are available for tests and implements many authentication mechanisms: Facebook, Twitter, form, basic auth, CAS, SAML, OpenID Connect, JWT...
The latest released version is the 
See the release notes. Learn more by browsing the pac4j documentation and the jee-pac4j Javadoc.
See the migration guide as well.
You can use the mailing lists or the commercial support.