HI, Everyone: A few months ago, I reported a problem that I had with Shibboleth (see below) and DSpace 6.0. I have been working on this issue off-and-on, and I finally solved it. It turns out that my problem was something that I had in my old DSpace 5.5 config that I carried over to my DSpace 6.0 local.cfg. The statement was: event.dispatcher.default.consumers = authority, versioning, discovery, eperson, harvester
Once I removed the statement from my local.cfg file, shibboleth started to work. I just wanted to warn anyone who upgrades from older DSpace to 6.0, to be careful of just carrying over config settings from their old version to 6.0. I spent a lot of time comparing settings, and I missed this one. -- *************************** George Kozak Digital Library Specialist Cornell University Library - IT 218 Olin Library Cornell University Ithaca, NY 14853 607-255-8924 g...@cornell.edu ---------- Forwarded message ---------- From: George Kozak <gkoz...@gmail.com> Date: Fri, Apr 7, 2017 at 2:34 PM Subject: Shibboleth problems in DSpace 6.0 To: DSpace Technical Support <dspace-tech@googlegroups.com> Hi... I upgraded to DSpace 6.0 from DSpace 5.5 (modified Mirage2 theme), and we discovered that we are having a Shibboleth login problem. The login works, but we end up with a message: "Authentication Failed". In the DSpace logs, I see: 2017-04-07 14:05:51,604 ERROR org.dspace.authenticate.ShibAuthentication @ Unable to successfully authenticate using shibboleth for user because of an exception.java.lang.IllegalStateException: Unable to aquire dispatcher named default -- 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 dspace-tech+unsubscr...@googlegroups.com. To post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
