• We need your help to unlock our rights.

    It's time for a fork.

    FORGEROCK has shuttered the open-source community, and no longer allows new development on their platform under a permissive license.


    Join the movement to put the right to develop open, extensible software for user authentication, authorization, and identity management back into the hands of the open-source development community.

  • Join the Movement

    Major work has been done. New releases are underway.


    All that ForgeRock has is based on OpenDS and OpenSSO – open-source projects
    originally created by Sun Microsystems. The community owns these projects
    just as much as FORGEROCK. Join us as we fork OpenAM 13.5, OpenDJ 3.5,
    and OpenIDM 5 to make them community projects once again.


    If you want to help, or want to know when and how you can start using a
    modern community fork, join us on GitHub, Google Groups, or Gitter

    using the links below.


















    No contribution is too small. Every person gives us more momentum.


    Google Groups

    Official Website
    (Wren Security)

  • Why is a fork necessary?

    Simply put, FORGEROCK no longer works with the community to develop software. Consider the evidence:

    Trunk access closed off

    November 2016

    Without prior notice, all of the "trunk" GIT repos on the FORGEROCK Stash server were switched to requiring commercial subscriptions to access.

    No official public statement was provided after the fact about this change.

    Public repositories rolled back

    December 2016

    After having closed off the main trunk, FORGEROCK moved forward by rolling all of the source code copies they had under the ForgeRock GitHub account to code from the last stable release, effectively erasing 8 to 12 months of code from public history.

    Maven access closed off

    March 2017

    Once again proceeding without any prior notice to the community, FORGEROCK switched the ForgeRock Maven repository to deny access to anyone other than paid commercial subscribers.


    The Maven repository previously hosted all of the artifacts required to build open-source copies of OpenAM, OpenDJ, and OpenIDM. Without Maven access, users who did not already have a local copy of these artifacts could no longer build these projects.

    Community site replaced with static page and
    JIRA write access discontinued

    April 2017

    Previously, the page at ForgeRock.org provided a wealth of information about where to find each project, how to get involved in the community, and how to contribute patches and bug reports back. Now, the page is merely a single static page designed to advertise the new platform, and then point to old copies of source code on GitHub.


    In addition, users who could previously log-in to the FORGEROCK JIRA issue tracker ("Bugster") can no longer log-in without a paid subscription, further shutting-out community members from contributing bug reports and commenting on tickets.

    Public repositories rolled back even further

    April 2017

    Initially, in December 2016, the GitHub repository for OpenAM was rolled back to code from version 13; OpenDJ to version 3.0; and OpenIDM version 4.


    Now, the copies that FORGEROCK links to from the static ForgeRock.org page are even older – OpenAM 11.0.3, OpenDJ 2.6.4, and OpenIDM 2.1.2.