Skip to content
Switch branches/tags
Go to file


Failed to load latest commit information.
Latest commit message
Commit time

OpenAM Community Edition 11.0.3

Traditionally delivered as six different products — SSO, adaptive authentication, strong authentication, federation, web services security and fine-grained entitlement enforcement — OpenAM now provides all this in a single, unified cross platform offering deployed as a .war file into a Java Servlet container such as Tomcat.

About the Community Version

Originally based on Sun MicroSystem's OpenSSO, ForgeRock have been developing and commercially supporting OpenAM since 2010. This version was originally released to ForgeRock customers in March 2015, and is now being released as our Community Edition without the ForgeRock binary licensing restrictions. It is well tested an has managed millions of identities in its lifetime.

To find out about the enterprise release of the ForgeRock platform here.

Getting Started with OpenAM

Binary Downloads are available via the GitHub releases page for the project here.

ForgeRock provide a comprehensive set of documents for OpenAM. They maybe found here and here.

The getting started guide is here


Issues are handled via the GitHub issues page for the project.

Security Policy

ForgeRock will create GitHub issues for any known security issues that are thought to affect the community edition. They will have a SECURITY label. Community members are responsible for fixing and testing any security issues.

What should I do if I find a new security issue?

If you find a new security issue in the community edition please send an email describing the issue and how it may be reproduced to Once we receive the email we will;

  • Confirm whether or not the vulnerability affects any currently supported versions and if so we will follow our standard security response process which will involve us publishing the GitHub issue as part of the security advisory process
  • If the issue does not affect any supported versions we will notify the reporter and request that they create a github issue directly

How to Collaborate

Collaborate by:

Code collaboration is done by creating an issue, discussing the changes in the issue. When the issue's been agreed then, fork, modify, test and submit a pull request.


The Code and binaries are covered under the CDDL 1.0 license. Essentially you may use the release binaries in production at your own risk.

Legal Disclaimer Bit

All components herein are provided AS IS and without a warranty of any kind by ForgeRock or any licensors of such code. ForgeRock and all licensors of such code disclaims all liability or obligations of such code and any use, distribution or operation of such code shall be exclusively subject to the licenses contained in each file and recipient is obligated to read and understand each such license before using the Software. Notwithstanding anything to the contrary, ForgeRock has no obligations for the use or support of such code under any ForgeRock license agreement.

How do I build it?

Best built on linux or OS X. Builds are possible on Windows, but more of a challenge.

Environment (Pre-requisites)

Software Version
Apache Maven 3.0.5
JDK version Oracle JDK 7
Git 1.7.6 or above

The Community Edition Releases are built using Oracle JDK 1.7.0_80

  1. Clone the repository, or Fork it and clone your Fork if you want to create pull requests: git clone
  2. cd openam-community-edition-11.0.3
  3. mvn clean install

Modifying the GitHub Project Page

The OpenAM Community Edition project pages are published via the gh-pages branch, which contains all the usual artifacts to create the web page. The GitHub page is served up directly from this branch by GitHub.

All the Links