When e.g. removing the firstname of a user who is activated for google apps for work, the listener will fail with the following traceback: 02.05.16 13:43:21.595 LISTENER ( PROCESS ) : gafw: Modified google account of user 'univention2'. Traceback (most recent call last): File "/usr/lib/univention-directory-listener/system/google-apps-user.py", line 322, in handler ol.modify_google_user(old, new) File "/usr/lib/pymodules/python2.7/univention/googleapps/listener.py", line 154, in modify_google_user ["{} ({}): {}".format(mod, ",".join(self.attrs["google_attribs"][mod]), new[mod]) for mod in modifications]) KeyError: 'givenName'
fixed in r69055
Reopen: The traceback is gone, but the value is not modified in the google cloud. I think it should be set to empty or to a random string, whichever is the default for the given value
No blocker for Bug 37949
(In reply to Erik Damrose from comment #2) > Reopen: The traceback is gone, but the value is not modified in the google > cloud. That's bad luck with the test. Deleting other properties works. familyName and givenName are mandatory attributes for Google and are being *restored* after removal by them. Try this: from univention.googleapps.handler import GappsHandler gh = GappsHandler(None) test02 = '100862214349746867174' gh.modify_user(test02, {"name": {"givenName": None}}) It will return the user resource: {.. u'name': {u'familyName': u'test02ln', u'fullName': u'abcdef test02ln'}, ..} Now run: gh.get_user(test02) It will return: {.. u'name': {u'familyName': u'test02ln', u'fullName': u'abcdef test02ln', u'givenName': u'abcdef'}, ..} Google has restored (or blocked) the deleted givenName. > I think it should be set to empty or to a random string, whichever is > the default for the given value I don't want to do that generally. That would mean that multiple-value properties (_all_ properties except name) cannot be deleted anymore. It would be possible however to give name:{familyName, givenName} a special treatment... ... done in r69062.
Verified with latest app release, i just forgot to close this bug