By now you have probably read the news about the ForgeRock Identity Platform 5.0 release.
This major platform update comes with many documentation changes and improvements:
- Access Management docs are now arranged to make it much easier for you to find all the details about new features and specific capabilities (User Self Service, OAuth 2.0, SSO, Authorization, and more). Since long-time readers who know where everything was might find this disconcerting at first, we also included a map to the new doc set. Don’t forget to check out Amster, too, which is new, and lets you do configuration as (file-based) artifacts.
- Identity Management is covered with the same titles as the previous platform update, but a lot of new features that make integration easier. (Integrated social identity provider support, better system connector support, additional audit event handlers, HSM support, etc.)
- Directory Services now has a Security Guide covering all the features for protecting your deployment, a new configuration reference, a bunch of smaller doc improvements, and full coverage of new features (LDAP proxy, native JSON syntax, tools improvements, documented HSM support, and so on).
- Identity Gateway docs now include a Deployment Guide aimed at those of you working in DevOps environments. They also cover all the new features, from the developer Studio to SSO filters and everything in between.
- Platform docs make their first appearance in the update. Try the DevOps examples, which point to a more cloud-friendly way of deploying the platform. And if you are new to ForgeRock software, start with the platform guide that maps the functional modules to the documentation that describes them.
Hope you have no trouble finding what you need.
ForgeRock still has open positions in many locations. One of those is for a writer based in our Vancouver, WA office (across the river from Portland, OR).
Be forewarned. This is challenging, hands-on technical writing and reverse engineering work. If you are looking for a gig where you can remain in your comfort zone, skip this one.
On the other hand, if you feel that most things worth doing are tough in the beginning, take a closer look and apply for the job.
Some of you have been looking for the latest ForgeRock docs.
They are still on BackStage:
OpenAM (latest release: 13.5)
OpenDJ (latest release: 3.5)
OpenIDM (latest release: 4.5)
OpenIG (latest release: 4.5)
Try the BackStage search engine, too. (Top of the page at https://backstage.forgerock.com/docs.)
ForgeRock doc tools 3.2.2 were released today.
This is a maintenance release, compatible with earlier 3.2.x releases.
ForgeRock doc tools 3.2.2 includes the following components:
This release resolves bugs and includes several improvements. For details, see the release notes.
Big thanks once again for enhancements, for identifying problems, and for help debugging.
Thanks to Chris Lee, Cristina Herraz, Joanne Henry, Lana Frost, Lori Goldman, David Goldsmith, Gene Hirayama, and Mike Jang for fixes, improvements, testing and bug reports.
Thanks also to the ForgeRock BackStage team for their help and continued improvements to release documentation.
OpenAM’s capabilities have grown significantly in the last few releases, with the result that even the product docs outgrew the old organization. Thanks to Chris Lee, Cristina Herraz, David Goldsmith, and Gene Hirayama, the draft docs are now arranged to make it easier to find just what you are looking for.
Instead of a guide-based doc set, what you see now are topic-oriented categories that bring you right to the features you want to use:
- Try OpenAM (up and running quickly, ready for evaluation)
- Access Management (authentication and single sign-on, authorization, RADIUS)
- Federation (OAuth 2.0, OpenID Connect 1.0, SAML, STS)
- User Services (self-registration, self-serve account and password management, self-serve sharing using UMA)
- Installation and Maintenance (plan, install, set up, upgrade, and maintain access management services)
- Extensibility (REST APIs, Java APIs and SPIs, C SDK)
- Policy Agents (for enforcing policy on web sites and in Java web applications)
Each guide is written so that you find everything about a topic in one place. Are you focused on centralizing access policies for authorization? Read the Authorization Guide. Interested in granting access to account info for modern mobile and web applications using OpenID Connect? See the OpenID Connect 1.0 Guide. Participating in a federation of SAML 2 providers? Check out the SAML 2.0 Guide.
Those of you who knew the old layout intimately are probably going to wonder, “Where did you move my stuff?” In fact, there is a guide for that, too. Having Trouble Finding Something? indicates where your stuff went, with tables of correspondence from each section in the old layout to the topic in the new layout.
Great to see this leap forward towards a topic-based documentation set for OpenAM!
Congratulations to Cedric on the release of docbkx-tools 2.0.17 earlier this week.
For those of you working with DocBook and Maven, docbkx-tools provides a plugin to generate output formats (HTML, PDF, etc.) as part of the Maven build, by applying the DocBook XSL stylesheets.
The 2.0.17 release adds some improvements, including support for DocBook XSL 1.79.1.
At ForgeRock, we have been relying on docbkx-tools since 2011. The next release of our doc build plugin is using 2.0.17. Upgrade was straightforward. The only issue that still needs fixing is olink support in chunked HTML.
ForgeRock doc tools 3.2.0 were released today.
This is a minor release, compatible with earlier 3.x releases, with one small exception. See the release notes for details.
ForgeRock doc tools 3.2.0 includes the following components:
This release brings several improvements and squashes a few bugs.
Big thanks once again to Chris Lee for enhancements to the Bootstrap-styled HTML (the default for draft, in-progress docs to read when trying nightly builds), for identifying problems, and for help debugging.
Thanks also to Joanne Henry, Lana Frost, Lori Goldman, David Goldsmith, Gene Hirayama, and Mike Jang for testing and bug reports.