Red Hat Bugzilla – Bug 1256967
profile update in raw format accepts bad config
Last modified: 2015-08-25 19:25:31 EDT
This bug is created as a clone of upstream ticket:
Updating a profile with bad profile data will appear to succeed. The new profile data will be saved to database, but will not be loaded correctly and existing profile data is used... until restart. Then the profile will be skipped because it does not load properly. Attempting to use, update or delete the profile will fail. Attempting to import a new profile will probably also fail, because the LDAP entry already exists.
A manual ldapmodify with good profile data can restore the situation.
Proposed fix: attempt to initialise profile with new profile data received in raw format BEFORE writing to database and returning from call. Bad data should result in status 400 with as much explanation as possible.