pac4j is a Profile & Authentication Client for Java (it's a global rebuilding of the scribe-up library). It targets all the protocols supporting the following mechanism :
- From the client application, redirect the user to the "provider" for authentication (HTTP 302)
- After successful authentication, redirect back the user from the "provider" to the client application (HTTP 302) and get the user credentials
- With these credentials, get the profile of the authenticated user (direct call from the client application to the "provider").
It has a very simple and unified API to support these 4 protocols on client side :
- OAuth (1.0 & 2.0)
- CAS (1.0, 2.0, SAML, logout & proxy)
- HTTP (form & basic auth authentications)
- OpenID.
There are 5 libraries implementing pac4j for the following environments :
- the CAS server (using the cas-server-support-pac4j library)
- the Play 2.x framework (using the play-pac4j_java, play-pac4j_scala2.9 and play-pac4j_scala2.10 libraries)
- any basic J2E environment (using the j2e-pac4j library)
- the Apache Shiro library (using the buji-pac4j library)
- the Spring Security library (using the spring-security-pac4j library).
It's available under the Apache 2 license.
This Maven project is composed of 6 modules :
- pac4j-core : this is the core module of the project with the core classes/interfaces :
- the Client interface is the main API of the project as it defines the mechanism that all clients must follow : getRedirectionUrl(WebContext), getCredentials(WebContext) and getUserProfile(Credentials)
- the Credentials class is the base class for all credentials
- the UserProfile class is the base class for all user profiles (it is associated with attributes definition and converters)
- the CommonProfile class inherits from the UserProfile class and implements all the common getters that profiles must have (getFirstName(), getEmail()...)
- the WebContext interface represents a web context which can be implemented in a J2E or another environment.
- pac4j-oauth : this module is dedicated to OAuth client support, it's the successor of the scribe-up library :
- the FacebookClient, TwitterClient... classes are the clients for all the providers : Facebook, Twitter...
- the OAuthCredentials class is the credentials for OAuth support
- the FacebookProfile, TwitterProfile... classes are the associated profiles, returned by the clients.
This module is based on the pac4j-core module, the scribe-java library for OAuth protocol support, the Jackson library for JSON parsing and the commons-lang3 library.
- pac4j-cas : this module is dedicated to CAS client support :
- the CasClient class is the client for CAS server (the CasProxyReceptor is dedicated to CAS proxy support)
- the CasCredentials class is the credentials for CAS support
- the CasProfile class is the user profile returned by the CasClient.
This module is based on the pac4j-core module and the Jasig CAS client.
- pac4j-http : this module is dedicated to HTTP protocol support :
- the FormClient & BasicAuthClient classes are the client for form and basic auth authentications
- the UsernamePasswordCredentials class is the username/password credentials in HTTP support
- the HttpProfile class is the user profile returned by the FormClient and BasicAuthClient.
This module is based on the pac4j-core module and the commons-codec library.
- pac4j-openid : this module is dedicated to OpenID protocol support :
- the MyOpenIdClient, GoogleOpenIdClient... are the clients for all the providers : MyOpenId, Google...
- the OpenIdCredentials class is the credentials for OpenID support
- the MyOpenIdProfile, GoogleOpenIdProfile class are the associated profiles, returned by the client.
This module is based on the pac4j-core module and the openid4java library.
- pac4j-test-cas : this module is made to test CAS support in pac4j.
Learn more by browsing the Javadoc.
Provider | Protocol | Maven dependency | Client class | Profile class |
---|---|---|---|---|
CAS server | CAS | pac4j-cas | CasClient & CasProxyReceptor | CasProfile |
CAS server using OAuth Wrapper | OAuth 2.0 | pac4j-oauth | CasOAuthWrapperClient | CasOAuthWrapperProfile |
DropBox | OAuth 1.0 | pac4j-oauth | DropBoxClient | DropBoxProfile |
OAuth 2.0 | pac4j-oauth | FacebookClient | FacebookProfile | |
GitHub | OAuth 2.0 | pac4j-oauth | GitHubClient | GitHubProfile |
OAuth 2.0 | pac4j-oauth | Google2Client | Google2Profile | |
OAuth 1.0 & 2.0 | pac4j-oauth | LinkedInClient & LinkedIn2Client | LinkedInProfile & LinkedIn2Profile | |
OAuth 1.0 | pac4j-oauth | TwitterClient | TwitterProfile | |
Windows Live | OAuth 2.0 | pac4j-oauth | WindowsLiveClient | WindowsLiveProfile |
WordPress | OAuth 2.0 | pac4j-oauth | WordPressClient | WordPressProfile |
Yahoo | OAuth 1.0 | pac4j-oauth | YahooClient | YahooProfile |
Web sites with basic auth authentication | HTTP | pac4j-http | BasicAuthClient | HttpProfile |
Web sites with form authentication | HTTP | pac4j-http | FormClient | HttpProfile |
MyOpenId | OpenID | pac4j-openid | MyOpenIdClient | MyOpenIdProfile |
OpenID | pac4j-openid | GoogleOpenIdClient | GoogleOpenIdProfile |
First, you have define the right dependency : pac4j-oauth for OAuth support or/and pac4j-cas for CAS support or/and pac4j-http for HTTP support or/and pac4j-openid for OpenID support. For example :
<dependency>
<groupId>org.pac4j</groupId>
<artifactId>pac4j-oauth</artifactId>
<version>1.4.1</version>
</dependency>
As the pac4j snapshots libraries are stored in the Sonatype snapshots repository, this repository may be added in the Maven pom.xml file :
<repository>
<id>sonatype-nexus-snapshots</id>
<name>Sonatype Nexus Snapshots</name>
<url>https://oss.sonatype.org/content/repositories/snapshots</url>
<releases>
<enabled>false</enabled>
</releases>
<snapshots>
<enabled>true</enabled>
</snapshots>
</repository>
If you want to authenticate and get the user profile from Facebook, you have to use the org.pac4j.oauth.client.FacebookClient :
// declare the client (use default scope and fields)
FacebookClient client = new FacebookClient(MY_KEY, MY_SECRET);
// define the client application callback url
client.setCallbackUrl("http://myserver/myapp/callbackUrl");
// send the user to Facebook for authentication and permissions
response.sendRedirect(client.getRedirectionUrl(new J2EContext(request, response)));
...after successfull authentication, in the client application, on the callback url (for Facebook)...
// get OAuth credentials
OAuthCredentials credentials = client.getCredentials(new J2EContext(request, response)));
// get the facebook profile
FacebookProfile facebookProfile = client.getUserProfile(credentials);
System.out.println("Hello : " + facebookProfile.getDisplayName() + " born the " + facebookProfile.getBirthday());
For integrating an application with a CAS server, you should use the org.pac4j.cas.client.CasClient :
// declare the client
CasClient client = new CasClient();
// define the client application callback url
client.setCallbackUrl("http://myserver/myapp/callbackUrl");
// send the user to the CAS server for authentication
response.sendRedirect(client.getRedirectionUrl(new J2EContext(request, response)));
...after successfull authentication, in the client application, on the callback url...
// get CAS credentials
CasCredentials credentials = client.getCredentials(new J2EContext(request, response)));
// get the CAS profile
CasProfile casProfile = client.getUserProfile(credentials);
System.out.println("Hello : " + casProfile.getAttribute("anAttribute"));
For proxy support, the org.pac4j.cas.client.CasProxyReceptor class must be used (on the same or new callback url) and declared with the CasClient class :
casClient.setCasProxyReceptor(new CasProxyReceptor());
// casClient.setAcceptAnyProxy(false);
// casClient.setAllowedProxyChains(proxies);
In this case, the org.pac4j.cas.profile.CasProxyProfile must be used to get proxy tickets for other CAS services :
CasProxyProfile casProxyProfile = (CasProxyProfile) casProfile;
String proxyTicket = casProxyProfile.getProxyTicketFor(anotherCasService);
To use form authentication in a web application, you should use the org.pac4j.http.client.FormClient class :
// declare the client
FormClient client = new FormClient("/myloginurl", new MyUsernamePasswordAuthenticator());
client.setCallbackUrl("http://myserver/myapp/callbackUrl");
// send the user to the form for authentication
response.sendRedirect(client.getRedirectionUrl(new J2EContext(request, response)));
...after successfull authentication...
// get username/password credentials
UsernamePasswordCredentials credentials = client.getCredentials(new J2EContext(request, response)));
// get the HTTP profile
HttpProfile httpProfile = client.getUserProfile(credentials);
System.out.println("Hello : " + httpProfile.getUsername());
To use basic auth authentication in a web application, you should use the org.pac4j.http.client.BasicAuthClient class :
// declare the client
BasicAuthClient client = new BasicAuthClient(new MyUsernamePasswordAuthenticator(), new UsernameProfileCreator());
To use myopenid.com for authentication, you should use the org.pac4j.openid.client.MyOpenIdClient class :
// declare the client
MyOpenIdClient client = new MyOpenIdClient();
client.setCallbackUrl("/callbackUrl");
// send the user to myopenid.com for authentication
// we assume the user identifier is in the "openIdUser" request parameter
response.sendRedirect(client.getRedirectionUrl(new J2EContext(request, response)));
...after successfull authentication, in the client application, on the callback url (for MyOpenId)...
// get the OpenID credentials
OpenIdCredentials credentials = client.getCredentials(new J2EContext(request, response)));
// get the myOpenID profile
MyOpenIdProfile profile = client.getUserProfile(credentials);
System.out.println("Hello : " + profile.getDisplayName());
If you use multiple clients, you can use more generic objects. All profiles inherit from the org.pac4j.core.profile.CommonProfile class :
// get credentials
Credentials credentials = client.getCredentials(new J2EContext(request, response)));
// get the common profile
CommonProfile commonProfile = client.getUserProfile(credentials);
System.out.println("Hello : " + commonProfile.getFirstName());
If you want to interact more with the OAuth providers (like Facebook), you can retrieve the access token from the (OAuth) profiles :
OAuthProfile oauthProfile = (OAuthProfile) commonProfile;
String accessToken = oauthProfile.getAccessToken();
// or
String accesstoken = facebookProfile.getAccessToken();
You can also group all clients on a single callback url by using the org.pac4j.core.client.Clients class :
Clients clients = new Clients("http://server/app/callbackUrl", fbClient, casClient, formClient myOpenIdClient);
// on the callback url, retrieve the right client
Client client = clients.findClient(new J2EContext(request, response)));
All methods of the clients may throw an unchecked org.pac4j.core.exception.TechnicalException, which could be trapped by an appropriate try/catch. The getCredentials(WebContext) method can throw a checked org.pac4j.core.exception.RequiresHttpAction, exception to require some additionnal HTTP action (redirection, basic auth...)
Even if you can use pac4j on its own, this library is used to be integrated with :
- the cas-server-support-pac4j module to add multi-protocols client support to the CAS server
- the play-pac4j library to add multi-protocols client support to the Play 2.x framework in Java and Scala
- the j2e-pac4j library to add multi-protocols client support to the J2E environment
- the buji-pac4j library to add multi-protocols client support to the Apache Shiro project
- the spring-security-pac4j library to add multi-protocols client support to Spring Security
Integration library | Protocol(s) supported | Based on | Demo webapp |
---|---|---|---|
cas-server-support-pac4j 4.0.0-RC2-SNAPSHOT | OAuth / CAS / OpenID | pac4j 1.4.0 | cas-pac4-oauth-demo |
cas-server-support-oauth 3.5.2 | OAuth | scribe-up 1.2.0 | cas-oauth-demo-3.5.x |
play-pac4j 1.1.0 | OAuth / CAS / OpenID / HTTP | pac4j 1.4.0 | play-pac4j-java-demo play-pac4j-scala-demo |
j2e-pac4j 1.0.0 | OAuth / CAS / OpenID / HTTP | pac4j 1.4.0 | j2e-pac4j-demo |
buji-pac4j 1.2.0 | OAuth / CAS / OpenID / HTTP | pac4j 1.4.0 | buji-pac4j-demo |
spring-security-pac4j 1.2.0 | OAuth / CAS / OpenID / HTTP | pac4j 1.4.0 | spring-security-pac4j-demo |
The current version 1.4.2-SNAPSHOT is under development. It's available on the Sonatype snapshots repository as a Maven dependency.
The last released version is the 1.4.1 :
<dependency>
<groupId>org.pac4j</groupId>
<artifactId>pac4j-core</artifactId>
<version>1.4.1</version>
</dependency>
See the release notes.
pac4j is tested by more than 300 unit, bench and integration tests (authentication processes are completely simulated using the HtmlUnit library).
To launch the tests, the nr Maven profile should be used. For example :
mvn clean install -Pnr
Use the js Maven profile for Javadoc and sources generation.
If you have any question, please use the following mailing lists :