In UDM the 'lastname' is a mandatory attribute, but 'firstname' isn't. In the Kelvin API 'firstname' is mandatory, which leads to a validation error when loading users from LDAP (UDM REST API) which do not have a 'firstname' → internal error → HTTP 500.
Why is firstname mandatory in the Kelvin API?
(In reply to Florian Best from comment #1) > Why is firstname mandatory in the Kelvin API? That's the bug to be fixed: it shouldn't be.
"firstname" is not required anymore: [feature/kelvin] 0d22ab994 Bug #52368: firstname is not a required attribute [feature/kelvin] b5a37c173 Bug #52368: allow empty firstname also in import config, fix test Test cleanup: [feature/kelvin] 083ede8ec Bug #52368: use 'exclude' argument to .dict() and .json() calls instead of deleting from the result A new image has not yet been created, as that will soon be done for Bug 52659 anyway.
Full reverse: The "firstname" attribute is kept as 'required'. The Kelvin API has been modified to provide a helpful error message in the HTTP 500 response in case a user is loaded from LDAP that has no firstname. the git branch was force pushed to remove previous commits. the only commit for this bug is now: [feature/kelvin] 81331a51d Bug #52368: add error details to HTTP 500 response in case of ValidationErrors
* It is now possible to chage the roles of users. See manual section `Changing a users roles <https://docs.software-univention.de/ucsschool-kelvin-rest-api/resource-users.html#changing-a-users-roles>`_ for details (Bug #52659). There is a typo in the changelog. Can you also move this line to a commit for the relevant bug? Otherwise it works fine for me. Can be build and prepared for the next Kelvin Release
New app version and image build will be done for Bug 52659 soon, so saving the time to do it here.