OpenAM is an "all-in-one" access management solution that provides the following features in a single unified project:
- Authentication
- Adaptive
- Strong
- Single sign-on (SSO)
- Authorization
- Entitlements
- Federation
- Web Services Security
OpenAM provides mobile support out of the box, with full OAuth 2.0 and OpenID Connect support - modern protocols that provide the most efficient method for developing secure native or HTML5 mobile applications optimized for bandwidth and CPU.
The project is led by ForgeRock who integrate the OpenAM, OpenIDM, OpenDJ, OpenICF, and OpenIG open source projects to provide a quality-assured Identity Platform. Support, professional services, and training are available for the Identity Platform, providing stability and safety for the management of your digital identities.
To find out more about the services ForgeRock provides, visit www.forgerock.com.
To view the OpenAM project page, which also contains all of the documentation, visit https://forgerock.org/openam/.
For a great place to start, take a look at [Getting Started With OpenAM] (https://forgerock.org/openam/doc/bootstrap/getting-started/index.html "Getting Started With OpenAM").
For further help and discussion, visit the community forums.
You can obtain the OpenAM Web Application Archive (WAR) file in the following ways:
The easiest way to try OpenAM is to download the WAR file and follow the Getting Started With OpenAM guide.
You can download either:
- An enterprise release build.
- The nightly build which contains the latest features and bug fixes, but may also contain in progress unstable features.
In order to build the project from the command line follow these steps:
You will need the following software to build your code.
| Software | Required Version |
|---|---|
| Java Development Kit | 1.7 and above |
| Maven | 3.1.0 and above |
| Git | 1.7.6 and above |
The following environment variables should be set:
JAVA_HOME- points to the location of the version of Java that Maven will use.MAVEN_OPTS- sets some options for the jvm when running Maven.
For example your environment variables might look something like this:
JAVA_HOME=/usr/jdk/jdk1.7.0_79.jdk
MAVEN_OPTS='-Xmx2g -Xms2g -XX:+CMSClassUnloadingEnabled -XX:MaxPermSize=512m'
The central project repository lives on the ForgeRock Bitbucket Server at https://stash.forgerock.org/projects/OPENAM.
Mirrors exist elsewhere (for example GitHub) but all contributions to the project are managed by using pull requests to the central repository.
There are two ways to get the code - if you want to run the code unmodified you can simply clone the central repo (or a reputable mirror):
git clone https://stash.forgerock.org/scm/openam/openam.git
If, however, you are considering contributing bug fixes, enhancements, or modifying the code you should fork the project and then clone your private fork, as described below:
- Create an account on BackStage - You can use these credentials to create pull requests, report bugs, and download the enterprise release builds.
- Log in to the Bitbucket Server using your BackStage account credentials.
- Fork the
openamproject. This will create a fork for you in your own area of Bitbucket Server. Click on your profile icon then select 'view profile' to see all your forks. - Clone your fork to your machine.
Obtaining the code this way will allow you to create pull requests later.
The OpenAM build process and dependencies are managed by Maven. The first time you build the project, Maven will pull down all the dependencies and Maven plugins required by the build, which can take a significant amount of time. Subsequent builds will be much faster!
cd openam
mvn clean install
Maven builds the binary in openam/openam-server/target. The file name format is OpenAM-<nextversion>-SNAPSHOT.war,
for example "OpenAM-14.0.0-SNAPSHOT.war".
ForgeRock undertake functional, performance, and security testing on the Identity Platform, including OpenAM. To license a fully tested build of the Identity Platform check out how to buy.
ForgeRock adhere to a set of coding standards. A set of checkstyle rules enforce these standards,
and may be run by building using the precommit Maven profile:
mvn clean install -P precommit
Some legacy code will fail, so if you are modifying an existing module you should run this profile before modifying the code, and then run the profile again after modifications to ensure the number of reported issues has not increased.
Unit tests are provided with the project and are run by Maven as part of the build. OpenAM uses the "TestNG" framework. Unit tests should be written for all new code.
You can run just the tests:
mvn test
Or build without running tests:
mvn clean install -DskipTests
All new code and modifications should be covered by unit tests.
ForgeRock provide a comprehensive set of documents for OpenAM, including getting started and installation guides:
There are many ways to contribute to the OpenAM project. You can contribute to the OpenAM Docs Project, report or submit bug fixes, or contribute extensions such as custom authentication modules, authentication scripts, policy scripts, dev ops scripts, and more.
ForgeRock produce an enterprise point release build. These builds use the versioning format X.0.0 (for example 12.0.0, 13.0.0) and are produced yearly. These builds are free to use for trials, proof of concept projects and so on. A license is required to use these builds in production.
Those with support contracts have access to sustaining releases that contain bug and security fixes. These builds use the versioning format 13.0.X (for example 13.0.1, 13.0.2). Those with support contracts also get access to quality-assured interim releases, such as OpenAM 13.5.0.
See the list of contributors who participated in this project.
This project is licensed under the Common Development and Distribution License (CDDL). The following text applies to both this file, and should also be included in all files in the project:
The contents of this file are subject to the terms of the Common Development and Distribution License (the License). You may not use this file except in compliance with the License.
You can obtain a copy of the License at legal/CDDLv1.0.txt. See the License for the specific language governing permission and limitations under the License.
When distributing Covered Software, include this CDDL Header Notice in each file and include the License file at legal/CDDLv1.0.txt. If applicable, add the following below the CDDL Header, with the fields enclosed by brackets [] replaced by your own identifying information: "Portions copyright [year] [name of copyright owner]".
Copyright 2016 ForgeRock AS.
To save you sifting through the readme looking for 'that link'...
- ForgeRock's commercial website
- ForgeRock's community website
- ForgeRock's BackStage server
- OpenAM Project Page
- Community Forums
- Enterprise Build Downloads
- Enterprise Documentation
- Nightly Build Downloads
- Nightly Documentation
- Central Project Repository
- Issue Tracking
- Contributors
- Coding Standards
- Contributions
- How to Buy
- Sun Microsystems.
- The founders of ForgeRock.
- The good things in life.