A confusing attribute resolver configuration

[Wessel, Keith]

Hi, all,

I think I'm in over my head here.

I'm trying to pull the givenName attribute from a couple of different sources: our campus LDAP for enterprise users and the departmental/gues OUs of Active Directory for guest users. I have data connectors defined for each, and this would be trivial if the attribute in both data sources was called givenName.

It's not.

We have givenName in AD. However, givenName in the LDAP is multi-valued and contains multiple values if the user has entered nicknames into our directory. The institutional official first name is in uiucEduFirstName.

What I'd like to do is have my attribute definition for givenName use the value of uiucEduFirstName from the campus LDAP and givenName from AD. The user will never exist in more than one place.

I thought I could do a scripted attribute definition to handle this, but since givenName appears in both sources and I don't want to use the one from the campus LDAP, I'm not sure how to tell the script to only use givenName from AD.

Is there a way to do this, or do I just need to change how things work in the LDAP?

Keith