- v1.0.0-latest-prod
|
Tip
|
The 2.x versions are Spring Boot 3 compatible. |
Fixed a bug where the Admin UI would allow adding augmentations on the AdminUser Views despite the AdminUser domain not supporting them by default.
Updated ExternalAdminUserModificationListener to honor tenant/app access values received on initial user creation.
Previously, the values for these fields were not initialized unless broadleaf.adminuser.access-level.manage-tenant-app-access-externally was enabled.
However, this meant values set by AuthenticationServices (both before and after AuthenticationServices version 2.3.0) would be ignored when a user was first created.
This was previously acceptable, as Auth and AdminUser would always set the same default initial values in their respective local states.
However, since Auth 2.3.0, the initial values sent by AuthenticationServices may differ (and may potentially be values defined internally rather than on the 3PIDP configuration).
For this reason, the listener has been updated to honor any value for those fields on initial user creation, regardless of whether broadleaf.adminuser.access-level.manage-tenant-app-access-externally is enabled or disabled.
Included all Global Components to the metadata response for augmented container components
Fixed an issue where fields in the User Profile Preferences form would be overridden by null values if they were not updated by the user.
This was due to the fact that the update endpoint for user profile preferences was implemented as a PATCH operation, and the incoming request body would only include fields that were updated by the user.
Taking into account that null values could be passed in to indicate that fields are emptied (Phone and Default Application ID can be emptied), a new update endpoint using a PUT operation was added to allow for a full update of the user profile preferences, and the PATCH endpoint is now deprecated.