Another day.. Another bug!!!
We use Google API to provision and manage users in GoogleApps via Google MA FIM/MIM.
I have recently found that when you make changes to a user’s orgUnitPath and send it as a patch / update to Google, the API does not confirm it by returning the value in the return. But the change is actually made and if you do a GET for the user you can see the modified orgUnitPath
It fails to do the same with Google API Explorer and OAUTH Playground
Request
|
|
PUT https://www.googleapis.com/admin/directory/v1/users/EMAILADDRESS?key={YOUR_API_KEY} { "orgUnitPath": "/AdditionalServices" } |
Response (no orgUnitPath is returned although change has been made)
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 |
200 OK - Show headers - { "kind": "admin#directory#user", "id": "103043262939656712601", "etag": "\"XXXXXXXXXXXXX\"", "primaryEmail": "XXXXXXXXX", "name": { "givenName": "XXXXX", "familyName": "XXXXXXX", "fullName": "XXXXXXXXXXXX" }, "isAdmin": true, "isDelegatedAdmin": false, "lastLoginTime": "2017-09-11T02:33:46.000Z", "creationTime": "2015-06-08T03:37:37.000Z", "agreedToTerms": true, "suspended": false, "changePasswordAtNextLogin": false, "ipWhitelisted": false, "emails": [ { "address": "XXXXXXXXXXXXXX", "primary": true }, { "address": "XXXXXXXXXXXXXX" } ], "addresses": [ { "type": "custom", "customType": "", "streetAddress": "" } ], "organizations": [ { "name": "", "customType": "" }, { "primary": true, "type": "work", "customType": "", "department": "", "location": "" } ], "phones": [ { "value": "", "type": "custom", "customType": "" } ], "nonEditableAliases": [ "" ], "customerId": "XXXXXXXX", "isMailboxSetup": true, "includeInGlobalAddressList": false } |
Google has confirmed this as a high priority bug (b/65534998) but its been a week since reported.. Their current workaround suggested is to use GET after doing a PUT or a PATCH and not rely on the current return values of them. Doesn’t really solve the issue for us in an extremely large environment and also means changing the code etc..
Keep calm and wait!!!
Like this:
Like Loading...
