[teiid-issues] [JBoss JIRA] Updated: (TEIID-217) LDAP Connector should provide a way to retrieve all values of an attribute that appears multiple times within a search result

[Michael Walker (JIRA)]

     [ https://issues.jboss.org/browse/TEIID-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Walker updated TEIID-217:
---------------------------------

    Attachment: LDAPSyncQueryExecution.java


This attached file contains the added code to support multi-valued attributes. This has been tested and deployed to production at a client site. 

You should be able to diff this file against the latest in Teiid and add in this functionality.

Documentation will need to be updated to indicate how to identify an attribute as multivalued (see comments).

> LDAP Connector should provide a way to retrieve all values of an attribute that appears multiple times within a search result
> -----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TEIID-217
>                 URL: https://issues.jboss.org/browse/TEIID-217
>             Project: Teiid
>          Issue Type: Feature Request
>          Components: LDAP Connector
>    Affects Versions: 6.0.0
>            Reporter: Michael Walker
>            Assignee: Michael Walker
>            Priority: Minor
>         Attachments: LDAPSyncQueryExecution.java
>
>
> If an attribute appears more than once, we should have some way to return all values. Currently, we only return one value, with no rhyme, reason, or determinism as to which one gets returned. Implementing this is difficult when multiple attributes appear more than once, of course. But a simple example of where this problem rears it's head is in modeling LDAP groups. Groups typically have repeating attributes to represent each member, and it would be nice to query all members of a given group, but impossible to do so with the current logic. 
> A sophisticated solution would create a normalized view of a DN, breaking out multi-valued attributes into a separate table that could be joined by a primary key. A simple solution might allow attributes to be flagged as "multi-valued", in which case, they could be maintained in a single denormalized table that represents all values in the DN. 
> If we build an importer for LDAP, we should consider how to best handle this issue in the importer design.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira