Apache Shiro :: Support :: pac4j core

Security extension for Shiro based on pac4j (core)

License	The Apache Software License, Version 2.0
Categories	pac4j Security
GroupId	io.buji
ArtifactId	buji-pac4j-core
Last Version	1.4.3
Release Date	Mar 14, 2016
Type	bundle
Description	Apache Shiro :: Support :: pac4j core Security extension for Shiro based on pac4j (core)

Download buji-pac4j-core

Filename	Size
buji-pac4j-core-1.4.3.pom
buji-pac4j-core-1.4.3.jar	7 KB
buji-pac4j-core-1.4.3-sources.jar	4 KB
buji-pac4j-core-1.4.3-javadoc.jar	47 KB

Dependencies

compile (3)

Group / Artifact	Type	Version
org.apache.shiro : shiro-core	jar	1.2.4
org.pac4j : pac4j-core	jar	1.8.7
org.slf4j : slf4j-api	jar	1.7.12

test (6)

Group / Artifact	Type	Version
junit : junit	jar	4.12
org.slf4j : slf4j-simple	jar	1.7.12
org.powermock : powermock-api-mockito	jar	1.6.4
org.powermock : powermock-module-junit4	jar	1.6.4
com.openpojo : openpojo	jar	0.8.3
org.ow2.asm : asm	jar	5.0.3

Project Modules

There are no modules declared in this project.

The buji-pac4j project is an easy and powerful security library for Shiro web applications and web services which supports authentication and authorization, but also advanced features like CSRF protection. It's based on Java 8, Shiro 1.7 and on the pac4j security engine v5. 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 - Google App Engine - Kerberos - LDAP - SQL - JWT - MongoDB - CouchDB - IP address - REST API

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

3. A matcher defines whether the SecurityFilter must be applied and can be used for additional web processing

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

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

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

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

Demo

The demo webapp: buji-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 , 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 buji-pac4j Javadoc.

See the migration guide as well.

Need help?

You can use the mailing lists or the commercial support.

Buji.io

Versions

Version
1.4.3 Mar 14, 2016
1.4.2 Mar 12, 2016
1.4.1 Jan 14, 2016
1.4.0 Dec 9, 2015
1.3.1 Apr 29, 2015
1.3.0 Oct 23, 2014