empty email attribute in LDAP causes exception

[AndyH010493]

Hello,

I am importing my users but am getting the below error. Would you be able to provide some insight on this please?

2017-05-23 12:31:05 31914 ERROR main - Unhandled exception
Traceback (most recent call last):
File "/home/adobesync/.pex/install/user_sync-2.1-py2-none-any.whl.5b02240d49b48000b66132a75942ae8ff00ba845/user_sync-2.1-py2-none-any.whl/user_sync/app.py", line 345, in main
begin_work(config_loader)
File "/home/adobesync/.pex/install/user_sync-2.1-py2-none-any.whl.5b02240d49b48000b66132a75942ae8ff00ba845/user_sync-2.1-py2-none-any.whl/user_sync/app.py", line 203, in begin_work
rule_processor.run(directory_groups, directory_connector, umapi_connectors)
File "/home/adobesync/.pex/install/user_sync-2.1-py2-none-any.whl.5b02240d49b48000b66132a75942ae8ff00ba845/user_sync-2.1-py2-none-any.whl/user_sync/rules.py", line 147, in run
self.read_desired_user_groups(directory_groups, directory_connector)
File "/home/adobesync/.pex/install/user_sync-2.1-py2-none-any.whl.5b02240d49b48000b66132a75942ae8ff00ba845/user_sync-2.1-py2-none-any.whl/user_sync/rules.py", line 293, in read_desired_user_groups
if not self.is_selected_user_key(user_key):
File "/home/adobesync/.pex/install/user_sync-2.1-py2-none-any.whl.5b02240d49b48000b66132a75942ae8ff00ba845/user_sync-2.1-py2-none-any.whl/user_sync/rules.py", line 406, in is_selected_user_key
username = self.get_username_from_user_key(user_key)
File "/home/adobesync/.pex/install/user_sync-2.1-py2-none-any.whl.5b02240d49b48000b66132a75942ae8ff00ba845/user_sync-2.1-py2-none-any.whl/user_sync/rules.py", line 901, in get_username_from_user_key
return self.parse_user_key(user_key)[1]
File "/home/adobesync/.pex/install/user_sync-2.1-py2-none-any.whl.5b02240d49b48000b66132a75942ae8ff00ba845/user_sync-2.1-py2-none-any.whl/user_sync/rules.py", line 898, in parse_user_key
return user_key.split(',')
AttributeError: 'NoneType' object has no attribute 'split'
2017-05-23 12:31:05 31914 INFO main - ========== End Run (User Sync version: 2.1) (Total time: 0:00:01)

Thanks
Andy

[adobeDan]

What's apparently happening here is that, when your directory is being read, there are None objects coming back for some of the users in the directory. We have not seen this before, and I can't really investigate it without having more of the log to look at. Can you upload an entire debug-level log for a run that has this error?

[AndyH010493]

Thank you for the information.

is there a flag for obtaining a debug-level log?

[adobeDan]

In your main user-sync-config.yml file, in the logging section (typically at the bottom), specify debug as the value for the file_log_level: setting. See the example file 1 user-sync-config.yml for details.

[AndyH010493]

I have sent you the log file via my company's file transfer service

[adobeDan]

I got the log, will take a look later today.

[AndyH010493]

Hello,

just wondering if there is any update on this?

Thanks
Andy

[adobeDan]

So sorry! I promise an update by end-of-day (Pacific Time) tomorrow!

[AndyH010493]

no worries and Thankyou

[adobeDan]

OK, so I can't be sure about this but I think I may have found the issue. It's looking to me like you have a user in your LDAP directory who has a defined email attribute but the value of that attribute is the empty string. That is an edge case that we should check for and catch, and it would lead to exactly the error in your log: there is a created directory user whose "user key" is the None value.

Can you please check to see if you have any users in your LDAP directory that have a defined "mail" attribute but for whom that attribute value is empty? If you can confirm that's the case, then I can be sure I've found the issue. Thanks!

[AndyH010493]

ok yes, it definitely appears to be the case. I ran a powershell script to pull a list of the users in my AD that have no mail attribute set and the user that the adobe sync tool fails at is one of the users that do not have a mail attribute

[adobeDan]

Thanks so much for the confirmation. I will catch this case and guard against it properly. Marking this as a bug.