[ 
https://issues.apache.org/jira/browse/OPENMEETINGS-964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14087965#comment-14087965
 ] 

Jarrod Holder commented on OPENMEETINGS-964:
--------------------------------------------

Thank you for your email.

Please note that I have received your message and will read it as soon as 
possible.

If you require technical assistance, please have your request listed on the 
helpdesk as this will be the fastest way for you to receive support.

If you are requesting a site to be blocked/unblocked, please email it to 
SiteBlocks.

Due to several high-priority projects, it may be several days before I am able 
to respond to your email.  I apologize for any inconvenience this may cause.  
However, I will respond to your inquiry as soon as possible.

If you have an emergency, please contact Kristy Barbee at the CO.



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

Maxim Solodovnik closed OPENMEETINGS-964.
-----------------------------------------





--
This message was sent by Atlassian JIRA
(v6.2#6252)



> LDAP login should be refactored
> -------------------------------
>
>                 Key: OPENMEETINGS-964
>                 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-964
>             Project: Openmeetings
>          Issue Type: Task
>          Components: LDAP
>    Affects Versions: 3.0.0
>            Reporter: Maxim Solodovnik
>            Assignee: Maxim Solodovnik
>             Fix For: 3.0.3, 3.1.0
>
>
> Detailed description is here OPENMEETINGS-943
> The correct way to handle this:
> First:
> if bind_dn and bind_pwd are set, first conect to the LDAP directory with 
> these credentials
> if empty, then just use an nonymous bind to the directory
> Then
> if OM is set to AuthLDAP=NONE, just use the connection to retrieve 
> informations from the directory
> -if OM is set to AuthLDAP=OPENLDAP (should be SEARCHANDBIND actually), search 
> for the userDN and then perform a bind to the directory with userDN/provided 
> PWD
> if OM is set to AuthLDAP=SIMPLEBIND, construct the userDN from the username, 
> the user attribute (for instance cn or uid), and the userBase, and then 
> perform a bind with userDN and provided PWD
> if OM is set to AuthLDAP=SIMPLE (to be backward compliant), let's try a bind 
> with the provided user/password



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to