I've had LDAP authentication working on my upgrade for the past couple of
months, but now I find that it's not working again. The only config change I've
made since I got it working is setting up the server to run through port 8443.
Would that affect authentication?
Thanks,
--
Karen Savage
On Wed, May 4, 2011 at 15:20, Savage, Karen R. karen_sav...@baylor.edu wrote:
I've had LDAP authentication working on my upgrade for the past couple of
months, but now I find that it's not working again. The only config change
I've made since I got it working is setting up the server to run
On Wed, May 4, 2011 at 15:37, helix84 heli...@centrum.sk wrote:
On Wed, May 4, 2011 at 15:20, Savage, Karen R. karen_sav...@baylor.edu
wrote:
I've had LDAP authentication working on my upgrade for the past couple of
months, but now I find that it's not working again. The only config change
Hi,
I'm trying to execute the create_administrator script, but I'm getting
this error message:
Exception in thread main java.lang.NoClassDefFoundError:
org/dspace/administer/CreateAdministrator
Caused by: java.lang.ClassNotFoundException:
org.dspace.administer.CreateAdministrator
at
Please, disregard what I wrote so far. I didn't notice this came from
the DSpace mailing list, not the Xerxes one.
Karen, I assume you changed the port your webserver is listening on.
This shouldn't have any influence on LDAP authentication in DSpace.
Might any other change slip by at the same
Ah, that explains why I wasn't able to find any of the files you were
referring to. :)
Yes, I set it up to listen through port 8443 rather than 8080.
I'm the only admin making changes to this server at this time, and
switching to port 8443 is the only thing I remember doing since getting
LDAP
On Wed, May 4, 2011 at 16:56, Savage, Karen R. karen_sav...@baylor.edu wrote:
Our live 1.3 instance hasn't been affected, but I'll check with the LDAP
guy in IT to make sure there haven't been any changes made on their end.
If the other instance works, then the mistake will probably be at your
Andrea and Mark:
I think that I have something funny going on. If I do a
curl http://127.0.0.1:8080/solr/statistics/admin/ on my test 1.7.1 server, I
get an error Failed to connect to 127.0.0.1
If I do it on my 1.6.2 install (which is on a different server), it works fine.
I suspect that I
Andrea and Mark (and anyone else who may be interested):
It turns out that someone switched the port that tomcat runs under on my test
server... and of course, I didn't initially check because I assumed that it
was running on 8080.
I should have known better. I am OK now.
George Kozak
Hi Peter,
I was looking at the DSpace REST API module today, and I too had errors
with getting null when viewing something like:
http://localhost:8080/restapi/communities/213.xml
...
Attached is my patch for fixing that. https://gist.github.com/952058
(I'd prefer not sending files to the
Hi Diogo,
As far as I know, the command to create an administrator has always
been:
[dspace]/bin/create-administrator
But 1.4 was a long time ago now, and my memory ain't that great. It
looks like you are running:
??/create_administrator
Also ensure that your dspace files are
On May 4, 2011, at 2:26 PM, George Stanley Kozak wrote:
Andrea and Mark (and anyone else who may be interested):
It turns out that someone switched the port that tomcat runs under on my test
server... and of course, I didn't initially check because I assumed that it
was running on 8080.
12 matches
Mail list logo
