Below you can find the answers depending on when this question was asked only for the sake of history.
ANSWER AFTER April 3, 2017
With recent changes to the business model, you can find key information you need to know:
- The latest versions of the main products were first renamed, but secondly, they were renamed the ForgeRock Identity Platform version:
- OpenAM 14.0.0 → Access Manager 5.0.0
- OpenDJ 4.0.0 → Directory Services 5.0.0
- OpenIDM 5.0.0 → Identity Management 5.0.0
- OpenIG 5.0.0 → Identity Gateway 5.0.0
- The products listed above were released under a commercial license, which means:
- ForgeRock source code (i.e., ForgeRock intellectual property) is not licensed under an open source license.
- All source code that is not exclusively owned by ForgeRock (for example, source code owned by Sun or the source that worked with it open source) will continue to be available under the CDDL license and may be obtained under forgerock.org .
- All ForgeRock IPs are licensed under an open source license.
- Products released under a commercial license can only be evaluated in 60 days.
- At the same time, the official release of new products released community releases for Open * products:
- Community publications are essentially the latest service versions of the latest versions of EOL products.
- Since these are maintenance versions, they should be more stable in the first place, but secondly a bit more secure (only slightly, since these versions have not been updated to include security fixes released since the initial version of these versions was released) .
- Community publications can be found in forgerock.imtqy.com
- With these new releases, each community member must decide for themselves: whether they want to upgrade to the latest but stable version of the EOL'd product, or whether they want to try their luck with the latest publications, but are likely to be less mature software versions (such as OpenAM 13.0.0 that were released before the business model change).
- Whether the community version will be released / updated by ForgeRock in the coming years is still unknown, such information has not been publicly provided.
Except for the official announcement by ForgeRock, please view this topic in the ForgeRock forum for more details.
Summarizing:
Open * products are still open source and freely available, however they have not been published to ForgeRock anymore. Whether new versions of the communities will be available is not yet known, but given the current example, each year the community will gain access to the EOL'd product version.
ANSWER BEFORE April 3, 2017
Here are some facts about projects and licensing in general:
- Only major releases are available, which means that the source code is available in the format of the SVN tag, while the binary file that can be downloaded from BackStage will have a binary license on it.
- A binary license allows people to test the product, but does not allow them to use these binaries in production environments without a support subscription.
- Service options are not publicly available either in the source or in binary format.
- Each project connecting line (or wizard) is publicly available, which means that every fix is available in one form or form, so with some luck it should be possible for the cherry to select important corrections from the trunk to your own special version of the service.
- Each product is relatively easy to build (with the possible exception of web agents), and therefore it should not be a big risk for your deployment (ForgeRock has clients who create their own artifacts for their deployment, so it’s not actually rocket science )
- Downloading artifacts from BackStage requires only some skills for working with agent-protected applications, here is an example curl command:
$ curl -O -H "Cookie: fr_sso_sess_prod=AQIC5w..." https://backstage.forgerock.com/downloads/enterprise/openam/openam12/12.0.0/OpenAM-12.0.0.war
- Unfortunately, in most releases there are some unpleasant errors, for them backporting is relatively simple, since the difference between the body and the last major version should not be too big, so you should be able to manually delete corrections. Since major releases take place every year or so, you won’t have to live long with these local changes. Fortunately,
- Projects have an active community, and getting help on any issues should not be too complicated (let it be a deployment problem or how to implement projects locally).
Perhaps I should mention that I am a ForgeRock employee, so please make my comments.
Just to clarify : when you build the trunk yourself, you do not need to buy a subscription. Only ForgeRock enterprise builds must include a binary license. When you create your own things, you create binaries, so you can simply decide to leave a binary license out of it.