You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@esme.apache.org by "Vladimir Ivanov (JIRA)" <ji...@apache.org> on 2011/04/24 02:09:05 UTC

[jira] [Updated] (ESME-135) Add LDAP to ESME

     [ https://issues.apache.org/jira/browse/ESME-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vladimir Ivanov updated ESME-135:
---------------------------------

    Attachment: ESMEUI.properties
                upw_login_form.html
                display_single_message.js

> Add LDAP to ESME
> ----------------
>
>                 Key: ESME-135
>                 URL: https://issues.apache.org/jira/browse/ESME-135
>             Project: Enterprise Social Messaging Environment (ESME)
>          Issue Type: New Feature
>          Components: Server
>    Affects Versions: 1.3
>            Reporter: Dick Hirsch
>             Fix For: 1.3
>
>         Attachments: ESMEUI.properties, display_single_message.js, upw_login_form.html
>
>
> Someone just added LDAP acess to lift (http://jgoday.wordpress.com/2009/11/27/lift-ldap/) . It would be create if someone tried this out in ESME. 
> There are bunch of things that still need to be discussed before this occurs.   How do we use the LDAP-based roles? As a basis for pools? Should we take user data from the LDAP? If so, how do we decide which parameters are necessary in ESME and what happens if they don't exist in the LDAP?

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