Report an issue of SWORD version 1 with multiple authentications on DSpace 9.2

20 views
Skip to first unread message

Joshua Kim

unread,
Apr 16, 2026, 9:27:47 AM (7 days ago) Apr 16
to DSpace Technical Support
Hello,

I am writing a report that when Orcid and native authentication are enabled with SWORD v1 on DSpace 9 .2 (we use Apache 2.4.x and Tomcat 10.x), there is a 401 error and a 500 error.

Thank you to those who responded to my request to fix the SWORD v1 issue on our server. 
When Shibboleth, Orcid, and native authentication are enabled with SWORD v1 on DSpace 9.2, there is a 401 error. After extensive trials, I found out that Orcid authentication returns null in dspace.log, so SWORD v1 authentication fails. When I disabled ORCID authentication, finally, SWORD v1 began to work. I want to provide ORCID authentication to our University members. Could someone please look into this issue and let me know how I can put ORCID back?

DSpace Technical Support

unread,
Apr 16, 2026, 1:03:41 PM (7 days ago) Apr 16
to DSpace Technical Support
This appears to have been answered in your other thread: https://groups.google.com/g/dspace-tech/c/su4c0l2nC2s/m/YLaHaqymAQAJ

As noted there, this is fixed by https://github.com/DSpace/DSpace/pull/12289 which will be in the DSpace 9.3 release.

I just wanted to link to that thread for more information, just in case others run into this same error.

Tim

mw...@iu.edu

unread,
Apr 17, 2026, 10:58:05 AM (6 days ago) Apr 17
to dspac...@googlegroups.com
On Thu, Apr 16, 2026 at 01:27:47PM +0000, Joshua Kim wrote:
> I am writing a report that when Orcid and native authentication are enabled with SWORD v1 on DSpace 9 .2 (we use Apache 2.4.x and Tomcat 10.x), there is a 401 error and a 500 error.
>
> Thank you to those who responded to my request to fix the SWORD v1 issue on our server.
> When Shibboleth, Orcid, and native authentication are enabled with SWORD v1 on DSpace 9.2, there is a 401 error. After extensive trials, I found out that Orcid authentication returns null in dspace.log, so SWORD v1 authentication fails. When I disabled ORCID authentication, finally, SWORD v1 began to work. I want to provide ORCID authentication to our University members. Could someone please look into this issue and let me know how I can put ORCID back?

I see that this has been addressed, but perhaps this local patch,
which we needed to make ORCiD person lookup work, is also relevant:

https://gist.github.com/mwoodiupui/06f6ef6a4a86930116348cf604ad6da8

It's against 9.1, which turned out to have at least two problems in
this area (an inadequate cookie processor and a try-with-resources
discarding response entities before they were read) as well as a
lamentable lack of debug logging. I need to see if these have been
fixed already and, if not, file a PR.

--
Mark H. Wood
Lead Technology Analyst

University Library
Indiana University Indianapolis
755 W. Michigan Street
Indianapolis, IN 46202
317-274-0749
library.indianapolis.iu.edu

ORCiD: 0000-0002-9558-3768
signature.asc
Reply all
Reply to author
Forward
0 new messages