Using proxyAddresses from Active Directory

[altinac]

We have several users that use some of their email aliases to email our implementation of OTRS. These users have those aliases populated within the proxyAddresses attributed within Active Directory. Is there a way to get OTRS to query that field to find the email address and which sAMAccountName attribute it is associated with?

We are using Active Directory as our Customer database instead of a local database to ensure our customer data is up to date.

[jojo]

yes,
adjust

CustomerUserPostMasterSearchFields => ['email'],

in the CustomerUser definition in your config

[altinac]

email is not a valid attribute in our directory.

I did find that if I put proxyAddresses into the CustomerUserSearchFields I can at least search for the sending email to find the right sAMAccountName. This is provided I set both the CustomerUserSearchPrefix and CustomerUserSearchSuffix to *. Of course, I have to do this manually after the ticket is created.

I'm wondering if there is a CustomerUserPostMasterSearchPrefix and CustomerUserPostMasterSearchSuffix option? I did try adding those to Config.pm, but it didn't work. Is there a way to get CustomerUserPostMasterSearchFields to use proxyAddresses, but add wildcards around the search string to ensure it finds the correct entry?

Thanks.

[jojo]

a ldap attribute only is allowed to contain one email address to have this working. you can have multiple attributes in the CustomerUserPostMasterSearchFields.

email should be a valid attribute in an AD. If not, repair your AD setup