November 2025 Update
This is likely the last update before TechEx and probably for 2025. I expect to be in Denver to provide an update and primarily discuss the status of the SP work and hopefully provide a short, uber-exciting demo of logging into a web site.
Business as usual on most fronts, so just some updates on key business:
Codeberg
IdP 5.2
SP 4
We have migrated a few more projects over to Codeberg as the master copy, mirroring back to us, and at this point I think we’re just waiting to pull the trigger on more of them. In parallel, I’ve adjusted our schema URLs into client-side redirects over to the resources in Codeberg and outside of a bug I fixed, have no reports of problems with that change, so that was a major step towards being able to shut down GitWeb for good, possibly before year’s end.
We are expecting Spring 7.0 to drop in the next week or so, which will start out “clock” to get IdP 5.2 out the door, but we have a few steps to take there. Spring Web Flow will have to produce a patch to fix a small issue or two so we will be forced to either wait for that or temporarily fork. We know they intend to produce a patch (because I asked) but we don’t know when, and the longer we delay, the shorter a window of life 5.2 will have, so we want to move expediently. But we also have testing to do before we’d feel comfortable shipping it, as the changes I made to the subject c14n design are a substantial regression risk. So I don’t know that we’ll be trying to ship it before January anyway, with holidays and TechEx and so forth. But it’s coming “soon”.
The progress on the SP has been very good, and at this point it’s becoming easier to actually talk about what’s left to get done than what’s been done:
Alternative Session Cache options, including the one we may end up using later as a default.
Cleaning up and finalizing some of the error handling features in the Agent
Audit logging in the Hub
OIDC support (possibly absent the Federation support initially, but we’ll see)
Logout – I’d like to at least get a local logout feature working for alpha, we’ll see
Documentation, documentation, and documentation
Much of that is not critical path for an alpha release, and we’re moving on getting the Agent packaged so it’s testable, so we are on track to get something out by end of year, if not by TechEx.
I’m also much more confident that we will be able to ship V4 by end of next year, practically for certain, which will finally get the clock started on sunsetting V3, though that’s still some years away.
If you haven’t perused the documentation that does exist, I encourage anybody using the SP now to do so, so you can make an honest determination as to your plans. I do not advise waiting on this. If it’s not what you want, then jump, and do it sooner than later. I would probably suggest that those with nicely partitioned development systems for their IdP that might be accessible to their organization’s systems consider deploying the Hub plugins there as a testing platform for others to use in trying out the new Agents for at least internal use against your IdP. It should help give people a sense of where the responsibility lines fall.
The docs:
I can say at this point that after the latest round of changes, the Agent config is pretty close to its final form right now, and the Hub is at least 80% stable, though much less well documented to this point. The Agent docs are quite far along except for bits that are literally going to be copied from V3 (e.g., the RequestMap), and a full treatment of all the content settings available, and some of the more advanced topics.