We are pleased to announce that version 4.3 of the Curity Identity Server is out.
A couple years ago, we certified the Curity Identity Server for most of the OpenID Foundation’s profiles of OpenID Connect. This new release conforms to all of those and is also self-certified to comply with the dynamic, form post, 3rd-party login, and the FAPI profiles.
We have also implemented support for Dynamic Client Registration Management (DCRM, RFC 7592). In our implementation, we’ve gone beyond the RFC with support for “management clients” that invoke the DCRM API on behalf of other dynamic clients.
PSD2 is live! This release provides a new feature that will use the DN of the certificate used to authenticate to the DCR endpoint. This will allow TPPs to not have to include it in the JSON posted during registration. If present in the body, it will continue to be accepted as long as it matches, ensuring backward compatibility. This works in non-PSD2 use cases as well, when mutual TLS is used on the DCR endpoint.
As with all releases, this one fixes many bugs and includes a number of smaller enhancements. We hope you enjoy using this release as much as we enjoyed building it!
This is just a selection of what’s new in the release, you can see the complete list of fixes and improvements in the release notes.