OpenIG Community Edition v2.1.0
Why OpenIG?
OpenIG is an independent policy enforcement point that reduces the proliferation of passwords and ensures consistent, secure access across multiple web apps and APIs. OpenIG can leverage any standards-compliant identity provider to integrate into your current architecture. Single sign-on and sign-off improves the user experience and will vastly improve adoption rates and consumption of services provided.
- Extend SSO to any Application
- Federate Enabling Applications
- Implement Standards Based Policy Enforcement
About the Community Version
ForgeRock created OpenIG Community Version from their End of Service Life Identity Platform. This code was first released as part of the ForgeRock Identity Platform in March 2012.
To find out about the enterprise release of the ForgeRock platform here.
How do I build it?
Environment
The code is built using Maven and is predominantly java based.
Versions to use:
Java - OpenJDK v1.6.0_41
Maven - v3.0.5
The output of mvn --version
should show the correct versions of both maven and java as below;
Apache Maven 3.0.5
Maven home: /usr/share/maven
Java version: 1.6.0_41, vendor: Sun Microsystems Inc.
Java home: /usr/lib/jvm/java-6-openjdk-amd64/jre
Default locale: en_GB, platform encoding: UTF-8
OS name: "linux", version: "3.13.0-108-generic", arch: "amd64", family: "unix"
Building the Code
Clone the repository and build:
git clone [email protected]:ForgeRock/openig-community-edition-2.1.0.git
cd openig-community-edition-2.1.0
mvn clean install
Modifying the GitHub Project Page
The OpenIG 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.
Getting Started with OpenIG
ForgeRock provide a comprehensive set of documents for OpenIG. They maybe found here.
Web versions:
Issues
Issues are handled via the GitHub issues page for the project.
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 submmit a pull request.
Licensing
The Code an binaries are covered under the CDDL 1.0 license.
All the Links
To save you wading through the README looking for 'that' link...