You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. Mapping the GoogleQuota attribute to None
2. Use the command syncOneUser add that user
3.
What is the expected output? What do you see instead?
I see this output:
Command: syncOneUser (uid=ivan)
The user record for uid=ivan,ou=personas,dc=cyc,dc=ull,dc=es is now:
Now looking up 'ivan' in Google Apps for Your Domain...
User 'ivan' not found
The recommended action for this user is to
treat user as having been: added
Proceed with that action (y/n) y
03-16 19:30 root ERROR error: ProvisioningApiError: **Error
on 'quota' argument: must be an integer
03-16 19:30 root ERROR failure to handle 'added' on
uid=ivan,ou=personas,dc=cyc,dc=ull,dc=es: ProvisioningApiError: **Error
on 'quota' argument: must be an integer
What version of the product are you using? On what operating system?
Google Apps LDAP Sync v1.2. Linux
Please provide any additional information below.
Original issue reported on code.google.com by aplatan...@gulic.org on 16 Mar 2008 at 7:34
The text was updated successfully, but these errors were encountered:
It works if the GoogleQuota attribute is mapped to None by changing directly
the
configuration file. For example:
mapping =
{'GoogleUsername': 'uid', 'GooglePassword': "Password", 'GoogleFirstName':
'givenName', 'GoogleLastName': 'sn', 'GoogleQuota':
None, 'GoogleApplyIPWhitelist': False}
The testFilter and mapGoogleAttribute commands map the attribute to 'None'. For
example:
mapping =
{'GoogleUsername': 'uid', 'GooglePassword': "Password", 'GoogleFirstName':
'givenName', 'GoogleLastName': 'sn', 'GoogleQuota': 'None',
'GoogleApplyIPWhitelist':
False}
And that causes the exception.
Original comment by aplatan...@gulic.org on 16 Mar 2008 at 8:25
Original issue reported on code.google.com by
aplatan...@gulic.org
on 16 Mar 2008 at 7:34The text was updated successfully, but these errors were encountered: