Details
-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
None
Description
From: grouper-users-request@internet2.edu grouper-users-request@internet2.edu On Behalf Of Liam Hoekenga
Sent: Wednesday, January 24, 2018 4:38 PM
To: grouper-users@internet2.edu
Subject: [grouper-users] subject.properties "virtual attribute" being passed to LDAP backend
We are constructing a virtual attribute in subject.properties to provide a description string..
subjectApi.source.ldap.param.subjectVirtualAttribute_0_searchAttribute0.value = ${subjectUtils.defaultIfBlank(subject.getAttributeValueOrCommaSeparated('UID'), "")},${subjectUtils.defaultIfBlank(subject.getAttributeValueOrCommaSeparated('CN'), "")},${subjectUtils.defaultIfBlank(subject.getAttributeValueOrCommaSeparated('ENTITYID'), "")}
|
We then tell the subjectApi to use that virtual attribute as the description...
subjectApi.source.ldap.param.Description_AttributeType.value = searchAttribute1
The subject mechanism includes searchAttribute1 in it's LDAP query. I'm confused as to why it does that if it's a virtual attribute?
Liam