Hello, Am 17.11.2007 um 03:53 schrieb Wolf Angel:
Please post back to the list as well using shift-reply. Thats common use on this list: I might not be able to help but somebody else can. I might not be reading my mail but somebody else on the list catches up. One day somebody will search the archives, finds your question, but has to ask it again because he finds no answer, rendering archives mostly useless. > The DSpace version 1.4.2, fine > I used Debian etch fine > the Java SDK is 1.4, Here we are I believe. Java 6 is current but not yet available on all platforms. Java 5 is still mainstream and broadly available. Java 4 is still acceptable *IF* it works, but I guess this could be your problem. No, I am not a programmer, I am an admin. I am doing Java for runaways. So I read the sources and find that in dspace.cfg, there are some values defined that contain the string ldap. I pick one of them, ldap.provi- der_url and search the sources. I get three source files as result, RegisterServlet.java, LDAPServlet.java, both from the webui dir and LDAPAuthetication.java which is part of the EPerson code. I look into it and find all of them using the javax.naming.Context Interface which turns out to be part of the implementation of the JNDI Java Naming and Directory Interface. Voila, Directory Inter- face, that makes sense for Lightweight Di- rectory Access. Then, take a look into the docs. The API descriptions sound very simi- lar in 1.4.2 and 1.5 but that does not say that it works the same way. Then for the release notes: <http://java.sun.com/j2se/1.5.0/docs/guide/jndi/index.html> <http://java.sun.com/j2se/1.4.2/docs/guide/jndi/index.html> Many of the changes mentioned here are in the javax.naming.ldap package which does not seem to be used in DSpace. But anyway it looks as if this Interface still re- ceives a lot of changes and attention and has not been very mature in 1.4.2 in turn. It might be worth a try updating. > postgres 8.2 fine > and Tomcat 5.1 I only knew 5.0 and 5.5; 6.x is current. You are well off with 5.5. Everything before I have not used with dspace. I think it is rather old and should be upgraded if you are at it in aptitude. So dspace.log doesnt tell a thing? Any details regarding the directory server and schema in use? A sample user record? The field mapping probably needs some tweaking and doesnt necessarily work out of the box. Bye, Christian > To configure the connection I fallow the instructions in the > install doc but > steel don´t work................ > > > 2007/11/11, Christian Voelker <[EMAIL PROTECTED]>: > Am 12.11.2007 um 02:06 schrieb Wolf Angel: > > > I have an Internal System Error when I conect DSpace to LDAP, > > according to the > > installation document I did all correctly, but isn't > > working...............any solution??? > > The dspace.log file might be a little bit > more verbose about what is really going on. > > There are endless possibilities: Which kind > of LDAP do you use, including version and > configuration information e.g. the method > of connection. I dont use LDAP but once > heard the older MS AD services versions > were using an uncommon schema for example. > > Also some basics about your dspace setup > including the JSP container in use, The > OS and Java version might be interesting. > > Bye, Christian > > > > > -- > May the Force be With You > GNU/Linux Registered User #436900 ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
