Aysegul Aydin wrote:
Hi,
I'm trying to configure LDAP in JetSpeed-2.2.0. I realized that the LDAP
documentation in JetSpeed 2 web page is obsolete since JetSpeed 2.2.0 source
code has a totally different security-ldap.xml file and also the classes that
are mentioned in the documentation no longer exist in JetSpeed 2.2.0 source.
I have tried to configure LDAP by my instincts :) but I couldn't succeed. Here
is what I have done:
- I have put an override.properties file in my portal project WEB-INF/conf/
directory. override.properties file's content is as follows:
#-------------------------------------------------------------------------
# LDAP
#-------------------------------------------------------------------------
#My LDAP Settings
ldap.url = ldap://localhost:10389
ldap.base =o=lbs
ldap.userDn = cn=admin,o=lbs
ldap.password =secret
ldap.context.factory=com.sun.jndi.ldap.LdapCtxFactory
ldap.user.filter = (objectclass=person)
ldap.search.scope = 2
ldap.user.searchBase=
ldap.user.entryPrefix=uid
ldap.role.searchBase=ou=Roles,o=Jetspeed
ldap.group.searchBase=ou=Groups,o=Jetspeed
#Turn on LDAP Security
spring.filter.key = portal.ldap
-------------------------------------------------------
<snip/>
I understand that it cannot find bean named
'org.apache.jetspeed.security.spi.SecurityDomainAccessManager' and it's
probably because this bean's j2:cat is defined as dbSecurity where I use
ldapSecurity. I deduced it from its spring definition which is in
security-spi.xml file:
<bean
class="org.springframework.beans.factory.config.BeanReferenceFactoryBean">
<meta key="j2:cat" value="dbSecurity" />
<meta key="j2:alias"
value="org.apache.jetspeed.security.spi.SecurityDomainAccessManager" />
<property name="targetBeanName"
value="org.apache.jetspeed.security.spi.JetspeedSecurityPersistenceManager" />
</bean>
Now I don't know what to do to fix this problem. We are planning to use
JetSpeed 2.2.0 portal with an LDAP integration to another web-application so it
is important that we can make it work. Thanks in advance for your support,
Hi Aysegul,
I'm not all to familiar with the LDAP configuration myself but it might be the default j2:cat configuration for the
SecurityDomainAccessManager is not sufficient for ldap usage.
First of all, I advise creating a new JIRA issue for this so we can properly
track this issue and assign someone to work on this with you.
I'd like to assign this to Dennis Dam as he has been working on both the LDAP and Domain security features the most, but he's away on
holiday this week, so bear with us for the time being :)
Furthermore, I just noticed we seem to have "misplaced" some of the new Jetspeed 2.2 security documentation with the restructuring of the
online website. Will look into recovering that and bring it back online.
Please note, most of the current online security documentation is still based upon Jetspeed 2.1.3. We're working hard to provide up to date
new documentation for 2.2 but that's a time consuming tasks all in itself.
An important but still limited overview of the new security model however is
available online here:
http://portals.apache.org/jetspeed-2/devguide/new-security.html
Back to your issue: I would try to enable the SecurityDomainAccessManager for
both dbSecurity and ldapSecurity and see if that fixes it.
You can do this by using <meta key="j2:cat" value="dbSecurity or ldapSecurity"/>
See also:
http://portals.apache.org/jetspeed-2/devguide/spring-config.html
Regards,
Ate
Aysegul AYDIN
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
