Custom attributes in extension-config not being applied?

[christopher-b]

I'm using some logic in extension-config.yml to override user's email and domain in certain cases, but it appears that users are still being created with keys using the default domain.

Many of our users have multiple email addresses, but we want to default to student email addresses when they exist. These are stored in a custom AD attribute OCADstudentEmail. I have the following after_mapping_hook in my config:

  student_email = source_attributes.get('OCADstudentEmail')
  if student_email is not None:
    target_attributes['email'] = student_email
    target_attributes['domain'] = student_email.split("@")[1]
  print(source_attributes)
  print(target_attributes)

Which gives the following output (filtered to a single user):

> ./user-sync -c config/user-sync-config.yml -t --user-filter user123
...
2018-06-13 12:26:03 351 INFO processor - ---------- Start Load from Directory -----------------------
{'email': 'user123@faculty.ocadu.ca', 'identity_type': None, 'username': 'user123', 'domain': None, 'givenName': 'User', 'sn': '123', 'c': 'CA', 'OCADstudentEmail': 'user123@student.ocadu.ca'}
{'email': 'user123@student.ocadu.ca', 'username': 'user123', 'domain': 'student.ocadu.ca', 'firstname': 'User', 'lastname': '123', 'country': 'CA'}
2018-06-13 12:26:05 351 INFO processor - ---------- End Load from Directory (Total time: 0:00:01) ---
2018-06-13 12:26:05 351 INFO processor - ---------- Start Sync with UMAPI ---------------------------
2018-06-13 12:26:07 351 INFO processor - Creating user with user key: federatedID,user123,faculty.ocadu.ca
...

Notice that the user key still references the faculty domain. Am I doing something wrong? Is overriding the domain this way not supported? Thanks.

[adorton-adobe]

The user key in that log message is derived from the directory user record, so it doesn't reflect the after-mapping hook.

(See https://github.com/adobe-apiplatform/user-sync.py/blob/v2/user_sync/rules.py#L903)

Try running the sync tool with the log level set to "debug". That will print the source and target attributes for each after-mapping hook invocation (so you don't have to print them) as well as the raw API calls made to create and update users. You should see the correct domain set in the raw API calls. If not, please let me know and I'll take a closer look.

[christopher-b]

Yes, the API call is setting the correct domain. Thanks for the clarification. It might help reduce confusion if the INFO output reflects info as updated in the hook.