The attribute data access feature of the JSON data source was updated to support sending additional parameters (parameter-mappings) to the backend even when the subject is provided in the URL path (url-path option).
parameter-mappings
url-path
In previous versions, parameters were only sent when the subject was provided by other means (e.g. query parameters); when using url-path any configured parameter-mappings were ignored. The Admin UI didn’t allow configuring parameter-mappings when using url-path, but it was still possible to configure them via the CLI or XML configuration, even if they were ignored.
In the unlikely case that you have configured parameter-mappings with url-path (previously ignored), note that those parameters will now be considered and included in the request to the backend. Refer to JSON / REST Data Source for details on the exact behavior.
In version 10.3.0, we’ve refreshed the symbols on the login pages to better align with our current UI design style. These assets had not been updated since version 7.0.
Note: If you need to revert to the previous symbols for any reason, they can still be found in the misc/ui-builder/src/curity/images_legacy directory.
misc/ui-builder/src/curity/images_legacy
In July 2025, new legal requirements for the digital accessibility of products and services will come into effect. These regulations are designed to ensure that digital solutions are inclusive and usable for all individuals, including people with disabilities.
BankID templates have been updated to improve the accessibility and usability of QR codes.
authenticator/bankid/launch/index.vm
consentor/bankid-signing-consentor/bankid-poller.vm