SynchronizingLDAPExtLoginModule

[nollie]

Hello

As part of an upgrade to portal 2.6 I'm experimenting with the SynchronizingLDAPExtLoginModule. I've read the Reference manual entry on the subject, but wanted to double check something.

This module will not allow, for example, the UserPortlet to change a password in LDAP, correct? I'd have to write an extension of this module to allow my users to change their LDAP password via the website?

Thanks

nollie

[bdaw]

Yes, synchronization is one way. LDAP --> DB. The source code is quite simple if you need to alter its behaviour:

http://anonsvn.jboss.org/repos/portal/branches/JBoss_Portal_Branch_2_6/identity/src/main/org/jboss/portal/identity/auth/SynchronizingLDAPExtLoginModule.java

[deanouk]

This source code seems to have moved for this class, and also for org.jboss.portal.identity.auth.IdentityLoginModule.

I can find neither within the Jboss Portal 2.6.4 source, nor subversion.

Can anyone point me in the right direction please?

[peterj]

The 2.6.4 source is in subversion at:

http://anonsvn.jboss.org/repos/portal/tags/JBoss_Portal_2_6_4/

The identity stuff has been moved into a subproject, you can find it at:

http://anonsvn.jboss.org/repos/portal/modules/identity/

In the 2.6.4 source download, after you run a build (go to build directory and run build script.bat or build.sh script) you can find the identity module in the directory thirdparty/jboss-portal/modules/identity. Unfortunately, the source is not there (it would be nice if the build pulled the sources also) but the manifest in the jar file should tell you which version it is and you can get the sources from subversion.

[deanouk]

Thanks Peter.

[deanouk]

Know how I can build the identity module?
The build script asks for a lot more than what's supplied.

[peterj]

I haven't built the entity module from scratch. What I usually do when I need to change something is to modify only the one file and compile only it, placing the identity jar file (and any other jars it needs) in my classpath. The compiler is then happy because it sees the related entity files. I then replace the class file in the entity jar with the newly compiled one.