Shibboleth authentication on DSpace 7.6 works only in Firefox; it does not work in Chrome and Edge.

[Manuela Ferreira]

Hello!

I was trying to configure Shibboleth authentication on DSpace 7.6: https://vitrinedocsabertos.dev.rnp.br/

After installing and configuring Shibboleth and Apache2 following the manual at https://wiki.lyrasis.org/display/DSDOC7x/Authentication+Plugins#AuthenticationPlugins-ShibbolethAuthentication, I can access the Shibboleth authentication page and successfully log in. However, after being redirected back to DSpace 7.6, the user appears logged in only when using Firefox. In Chrome and Edge, DSpace returns without displaying any login, even though /Shibboleth.sso/Session shows a valid login.

I've checked the logs for Shibboleth, DSpace, and Apache, but I haven't been able to find any errors.

Has anyone else encountered this issue?

Thank you in advance,

Manuela Klanovicz Ferreira

[Manuela Ferreira]

Hi!

I still haven't solved it.

Anyone else with the same problem?

Thank you

Manuela Klanovicz Ferreira 

[DSpace Technical Support]

Hi Manuela,

Could you follow the troubleshooting guide and look for errors in the User Interface (via your Firefox's DevTools)?  https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)

My best guess is an error is occurring *in the User Interface* when it runs in Firefox.  We did find some similar Firefox specific bugs recently & released fixes in the brand new 7.6.1 release.  So, it's also possible that 7.6.1 may have fixed this issue (not certain though). https://wiki.lyrasis.org/display/DSDOC7x/Release+Notes#ReleaseNotes-7.6.1ReleaseNotes

In any case, finding the error using the Troubleshooting guide is the best way to figure out the problem.  Feel free to share it on this list if the error you find doesn't make sense.

Tim

[DSpace Technical Support]

Apologies, I realized you said it *works* in Firefox, but not Chrome.  I misread that.  But, the solution is the same... check for errors in Chrome or Edge.

I have not heard of this behavior before, so it might be a configuration issue.  But, we'd know more if you can find the error message in your browser's DevTools (or similar).

Tim