...
We have begun to accelerate the pace of work on the backlog to completing IdP V5 and will be pushing hard over the next few weeks to complete whatever is left and make a beta available. Internal “live” testing on real world configurations will start soon. With the OIDC releases done and a few weeks gone by, we will be branching all the plugins and beginning work on porting them to V5. Most plugins will require an update, but there should be few deployer changes needed apart from the same sorts of adjustments common to all of the IdP configuration in a few mechanical areas.
Significant time was spent over the last month reviewing proposals around extending the metric information available, and making some adjustments to how existing metrics are named and reported to align the old with the new. A number of new metrics have been added at Internet2’s request to expose information about the configuration, such as metadata sources and filters used and relying party overrides applied. Additionally, a new diagnostic tool has been implemented that exposes a summary of the profile settings applied to particular requests (see Configuration Reporting).
The documentation for V5 has been created and a fair amount of progress cleaning up the V4 material has been made. The space is now public with a warning at the top. My general approach has been to treat the V5 documentation as a description of how a new install would look and feel, to avoid the constant caveats of “if you upgraded from 4.0 or earlier, this is different…”. Those operating with older configurations that predate V4.1 will be best served with the V4 documentation that speaks to some of that, or can take the opportunity during this year to modernize things (per this and this). We fully intend and expect that most of the “older” ways of doing this should continue to work.
...