Fix projection query field mapping issue #573
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using projection queries with entities that have @Attribute annotations for LDAP field mapping, the query was using Java field names instead of the mapped LDAP attribute names. This caused queries to fail when the Java field name differs from the LDAP attribute name.
Changes:
Example: For an entity field 'groupId' mapped to LDAP attribute 'gidNumber' via @Attribute annotation, projection queries now correctly use 'gidNumber' in the LDAP query.
Fixes projection queries for entities with custom LDAP attribute mappings.