I'm trying to get Shibboleth to work with a new DSpace 6 installation on
Centos 7 running Apache 2.4. I have both password and Shibboleth
authentication enabled. This gives me the opportunity to hover over the
Shibboleth login link. The link shows this URL:
https://rc.library.ourschool.edu/S
I'm trying to get Shibboleth to work with a new DSpace 6 installation on
Centos 7 running Apache 2.4. I have both password and Shibboleth
authentication enabled. This gives me the opportunity to hover over the
Shibboleth login link. The link shows this URL:
https://rc.library.ourschool.edu/S
Tim,
Thanks for your reply. After a lot of head-scratching, we found that the
Apache directive, "ProxyPreserveHost On" was necessary to make Shibboleth
create the proper target URL for callback. So now the end of our virtual
server config file looks like this:
ProxyPreserveHost On
We are using Vireo 3.0.6 (with Sword v1) and publishing to a DSpace 6.3
repository. Since updating the operating systems on both servers, Vireo
can’t connect to the DSpace repository to deposit theses and
dissertations. The DSpace server is running Amazon Linux kernel
4.14.88-72.73.amzn1.x8
Michael,
Thanks for the suggestion. I checked the cert and got "Verify return code:
21 (unable to verify the first certificate)". I added the required
CA-bundle and restarted Apache. Now when I check the cert I get "Verify
return code: 0 (ok)".
But Sword still says, "Unauthorized Credential
Further information:
We seem to have got past "unauthorized credentials."
Now Vireo says, "Unable to communicate with deposit location:
org.purl.sword.client.SWORDClientException: Received error from service
document request: Code: 400, Message: 'Bad Request'
Using curl to browse to the Sword
Further information:
We seem to have got past "unauthorized credentials."
Now Vireo says, "Unable to communicate with deposit location:
org.purl.sword.client.SWORDClientException: Received error from service
document request: Code: 400, Message: 'Bad Request'
Using curl to browse to the Sword
This problem was caused by the Sword configuration on the DSpace server.
Or, more precisely, the complete lack of configuration of the Sword
module. We moved the server from another host last summer, and that must
be when the config got overwritten with the defaults. Apparently, no one
had t
I would like to propose that a method for changing a user's DSpace password
be added to the DSpace admin tools. I know it is possible to change a
password using the "forgot password" link, but that requires access to the
user's email. In addition, it requires access to the "forgot password"
l
Yes, now I see that a new button appears in the user's profile after this
option is enabled and Tomcat restarted. The "Login as E-Person" button
allows an administrator to view the user's profile and reset the password
in the web interface. Thanks for pointing this out.
Glenn
On Monday, Jan
10 matches
Mail list logo