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

On Thursday, April 16, 2026 at 8:27:47 AM UTC-5 [email protected] wrote:

> 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?
>

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://lyrasis.org/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/dspace-tech/4650420f-98ed-4013-93cb-07d98edbf885n%40googlegroups.com.

Reply via email to