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.
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.
Last week ForgeRock released a platform update, including many new features. One of those features is support for User-Managed Access (UMA). UMA is a profile of OAuth 2.0 that allows resource owners to share their resources with others in a standard way. UMA puts resource owners in charge of defining policies for accessing their resources. From that perspective, UMA could be seen as highly scalable delegated policy administration.
At a level closer to the implementation, UMA describes how authorization servers, resource servers, and UMA clients interact to enable resource sharing. In the ForgeRock platform, OpenAM plays the role of authorization server. OpenIG plays the role of resource server. (These are currently the working parts of OpenUMA.) In the present implementation, the client side is for you to implement, although the OpenIG docs include an example client, and there are ForgeRock demos that cover the client side as well. You can download OpenAM 13 and OpenIG 4 from the ForgeRock BackStage downloads page.
To get started with OpenAM authorization server implementation, install OpenAM and then have a look at the Administration Guide chapter on Managing UMA Authorization.
This is a minor release, compatible with 3.0.0. See the release notes for details.
ForgeRock doc tools 3.1.0 includes the following components:
This release adds a few improvements and resolves a number of bugs.
One of the improvements is initial support for Asciidoc. The doc build plugin generates DocBook from Asciidoc source, and then processes the resulting output in the same way as other documents. At this time the doc build plugin does not allow you to mix Asciidoc and DocBook in the same document. For details, see the README.
Thanks to Peter Major for providing a new release of docbook-linktester, improving the link check usability with a more human-readable report, better supporting <olink> elements, and troubleshooting an issue related to throttling that affected link checks for some documents.
Thanks again to Chris Lee for a number of improvements to Bootstrap HTML output, and for fixing inter-document links in PDF (depends on the renderer, seen to work with Adobe Acrobat).
Thanks also to Lana Frost, Chris Clifton, David Goldsmith, Gene Hirayama, and Mike Jang for testing and bug reports.
Okay… this has nothing to do with the rest of the posts here… but we’ve been waiting so long, only to be disappointed.
A long time ago, back when Quake and even Doom seemed cool, there was a first-person-shooter that combined playability with humor so bad it was actually good. I’m talking about Duke Nukem 3D.
What I enjoyed about the jokes and sci-fi references was how the game went so over the top it seemed actually to make fun of itself, thus neutralizing the offensiveness. Duke Nukem 3D even seemed Kafkaesque at times, though in Fletch kind of way.
Looks like the one of the most delayed remakes in history is not worth the wait. So even if I did have one of the platforms it runs on, I would not be rushing to download a copy.
Gee, maybe I’ll have to read a book instead. Or write one.