You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by "mike long (JIRA)" <je...@jakarta.apache.org> on 2005/01/14 22:09:17 UTC
[jira] Commented: (JS2-188) Implement the LDAP
[ http://issues.apache.org/jira/browse/JS2-188?page=comments#action_57641 ]
mike long commented on JS2-188:
-------------------------------
Dear Edgar and Others interested in Jetspeed-2 and LDAP;
I have spent the last couple of days thinking about the needs of our team here at Dataline. I have reviewed David Le Strat's LDAP authentication classes as well. I can think of a few requirements issues that I would like to discuss with this community.
1) Do any of you need LDAP authorization as well? In addition to LDAP authentication, we need LDAP authorization. I see from looking at the Jetspeed-2 code that at least two interfaces exist which need LDAP implementations: GroupSecurityHandler and RoleSecurityHandler.
2) Should this "first cut" of LDAP authentication include digest-based authentication, where the hashed password of a user is compared to the hash generated by the user when attempting to login? Doing so would save looking up the user, getting their DN, and then authenticating them. We really need that kind of performance here.
Please forgive me if I am not using JIRA correctly. This is my first use of it. I will be gone until Tuesday and look forward to your comments.
Sincerely,
Mike Long
> Implement the LDAP
> ------------------
>
> Key: JS2-188
> URL: http://issues.apache.org/jira/browse/JS2-188
> Project: Jetspeed 2
> Type: Improvement
> Components: Security
> Reporter: J, Edgar Zavala
>
> Implement the LDAP integration using the SPI, provide the LDAP authenitcation option.
> TODO:
> 1.- Complete the current implementation and complete the David work in:
> a) org.apache.jetspeed.security.spi.impl.LdapCredentialHandler
> b) org.apache.jetspeed.security.spi.impl.LdapUserSecurityHandler
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: [jira] Commented: (JS2-188) Implement the LDAP
Posted by Marcel Dullaart <ma...@gmail.com>.
>
> I think that this implementation should be standards based, open
> source and free of any specific product rules, in this case for the
> LDAP part we need to include all the authentication mechanisms
> (anonymous, simple {clear text passwords}, SASL and kerberos 4) in
> some way, but i don't know exactly how will do that =/ (research in
> progress ;)).
>
I can certainly agree that it should be free of any specific product
rules, but it should be extendible such that product rule scaneasily
be included.
Since the target is standards based, will it be using JAAS for authentication?
Regards,
Marcel
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: [jira] Commented: (JS2-188) Implement the LDAP
Posted by Edgar Zavala <je...@gmail.com>.
Mike,
> 1) Do any of you need LDAP authorization as well? In addition to LDAP authentication, we need LDAP authorization. I see from looking at the Jetspeed-2 code that at least two interfaces exist which need LDAP implementations: GroupSecurityHandler and RoleSecurityHandler.
I believe that this implementation should include the
authorization, authentication and probably the 'user profile' storage
or mapping. In a first stage an authentication model will be
implemented (i think) and then the authorization part ( and profile
storage/mapping {i hope so =)} ).
> 2) Should this "first cut" of LDAP authentication include digest-based authentication, where the hashed password of a user is compared to the hash generated by the user when attempting to login? Doing so would save looking up the user, getting their DN, and then authenticating them. We really need that kind of performance here.
I think that this implementation should be standards based, open
source and free of any specific product rules, in this case for the
LDAP part we need to include all the authentication mechanisms
(anonymous, simple {clear text passwords}, SASL and kerberos 4) in
some way, but i don't know exactly how will do that =/ (research in
progress ;)).
> Please forgive me if I am not using JIRA correctly. This is my first use of it.
Is my fist JIRA use too.
Regards,
--
J. Edgar Zavala S. ak'a Kerberos
eMail: jezavala at gmail.com | jezs at kerberos-research dot com
PGP: 0x6B60B604/0x73C6D26B
Web: http://www.kerberos-research.org
-- My software never has bugs.It just develops random features --
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org