Skip to content
Security library for JEE: OAuth, CAS, SAML, OpenID Connect, LDAP, JWT...
Java Shell
Branch: master
Clone or download

Latest commit

Files

Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
src/main/java/org/pac4j/jee add constructor with matchers Mar 20, 2020
travis do not deploy PR Jul 21, 2015
.gitignore update README Apr 6, 2020
.travis.yml Update .travis.yml Mar 6, 2020
LICENSE
NOTICE Upgrade to pac4j v1.9 Mar 18, 2016
README.md update README Apr 6, 2020
pom.xml update to pac4j v4.0.2-SNAPSHOT May 28, 2020
renovate.json Add renovate.json (#49) Dec 10, 2019

README.md

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 Java 8, JavaEE 7 and on the pac4j security engine v4. 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 applications authentication while a direct client is for web services authentication:

▸ OAuth - SAML - CAS - OpenID Connect - HTTP - OpenID - Google App Engine - Kerberos - LDAP - SQL - JWT - MongoDB - CouchDB - 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. A matcher defines whether the SecurityFilter must be applied and can be used for additional web processing

  2. The SecurityFilter 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

  3. The CallbackFilter finishes the login process for an indirect client

  4. The LogoutFilter logs out the user from the application and triggers the logout at the identity provider level

  5. The JEEContext and the ProfileManager components can be injected

  6. The FilterHelper handles the filters and their related mappings.

Usage

1) Add the required dependencies

2) Define:

- the security configuration

- the callback configuration, only for web applications

- the logout configuration

3) Apply security

4) Get the authenticated user profiles

Demos

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...

Versions

The latest released version is the Maven Central, available in the Maven central repository. The next version is under development.

See the release notes. Learn more by browsing the pac4j documentation and the jee-pac4j Javadoc.

See the migration guide as well.

Need help?

If you need commercial support (premium support or new/specific features), contact us at info@pac4j.org.

If you have any questions, want to contribute or be notified about the new releases and security fixes, please subscribe to the following mailing lists:

You can’t perform that action at this time.