Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <1190581255.1248675855101.JavaMail.jira@brutus>
Date: Sun, 26 Jul 2009 23:24:15 -0700 (PDT)
From: "David Jencks (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Commented: (GERONIMO-4513) LDAP Realm Improvements
In-Reply-To: <2091508321.1231929900227.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/GERONIMO-4513?page=3Dcom.atlass=
ian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1=
2735493#action_12735493 ]=20

David Jencks commented on GERONIMO-4513:
----------------------------------------

Any chance you could supply a patch, at least for the login module?  Workin=
g on this would be 10X easier for someone who already has ldap set up.

> LDAP Realm Improvements
> -----------------------
>
>                 Key: GERONIMO-4513
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4513
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues)=20
>          Components: security
>    Affects Versions: 2.1.3
>            Reporter: J=C3=BCrgen Weber
>            Priority: Blocker
>             Fix For: 2.2
>
>
> I suggest several important improvements to the LDAP Realm, generally LDA=
P Realm should support the features of Tomcat's JNDIRealm (http://tomcat.ap=
ache.org/tomcat-6.0-doc/realm-howto.html#JNDIRealm)
> 1. a plan should be deployable from the console
> 2. LDAP Realm should allow anonymous bind (this is cause for "blocker")
> 3. I guess "User Role Search String" means a user attribute the role name=
s are taken from (same as Tomcat's userRoleName property). If this is set, =
all other role-related attributes should not be necessary. Generally, it sh=
ould not be necessary to have role-related attributes at all, if you only w=
ant the users to log in, but have <role-name>*</role-name>
> 4. if "Role User Search String" is empty, there is the wrong error messag=
e "option-roleSearchMatching must not be empty"
> There is no Role SearchMatching on the dialog
> 5. On the Test Results page: if the test fails, there is only
> =09Login Failed: LDAP Error
>     There should also be the error message and even stacktrace (right now=
 it's in the server log)

--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.