[teiid-issues] [JBoss JIRA] Updated: (TEIID-225) LDAP Connector should use base DN for table as base DN for updates as well as queries

[Steven Hawkins (JIRA)]

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

Steven Hawkins updated TEIID-225:
---------------------------------

    Fix Version/s: 7.3
                       (was: 7.2)


pushing to 7.3

> LDAP Connector should use base DN for table as base DN for updates as well as queries
> -------------------------------------------------------------------------------------
>
>                 Key: TEIID-225
>                 URL: https://jira.jboss.org/browse/TEIID-225
>             Project: Teiid
>          Issue Type: Feature Request
>          Components: LDAP Connector
>    Affects Versions: 6.0.0
>         Environment: MetaMatrix 5.5.3RC2
>            Reporter: Greg Haber
>            Priority: Minor
>             Fix For: 7.3
>
>
> Ramesh had a great idea earlier today on the LDAP connector:
> [Ramesh] Why not search base info along with PK information to build the unique
> DN? That seems possible right?
> [Greg] Yes, that is a great idea! I will put in a JIRA for that (small code change, changing name of "search base" to just "base", and doc change).  Probably we should have both relative and fully qualified DNs accepted here.  Note however that the base may be several levels higher up in the tree then where you want to put the entry, so the base DN may be "ou=people,dc=company,dc=com", with a relative DN of "uid=ghaber,ou=newyork" here.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira