Hi Alan, I googled around for "Tomcat 8.5" and "Session Cookie" and found this: http://tomcat.10.x6.nabble.com/cookie-related-regression-in-Tomcat-8-5-td5054371.html
At least someone else has encountered differences between how cookies are handled in Tomcat 8.0 and 8.5. Maybe this problem is similar, and somehow the DSpace session cookie is failing validation? FWIW, I've not yet tried running DSpace on Tomcat 8.5, as I'm still using 8.0 everywhere. It's possible you've hit a bug that is very specific to running DSpace on Tomcat 8.5. (Which, if verified, should be logged as a bug in the JIRA issue tracker) Tim On Mon, Jan 7, 2019 at 2:27 PM Alan Orth <alan.o...@gmail.com> wrote: > Dear list, > > Another data point in this mystery: I have just built a clean version of > DSpace 6.3 from the dspace-6.3 tag and I see the same behavior regarding > the lack of the `dspace.current.user.id` session cookie in XMLUI when > running under Tomcat 8.5.37. So it seems like it's a Tomcat configuration > issue or behavioral change in Tomcat 8.5.x. Anyone know where to look for > this? > > Regards, > > On Sun, Jan 6, 2019 at 11:49 AM Alan Orth <alan.o...@gmail.com> wrote: > >> Dear list, >> >> I have just built a clean vanilla version of DSpace 5.8 from the >> dspace-5.8 tag and I see the same behavior when running with Tomcat 8.5.x, >> so it is not a configuration problem with our customized DSpace. Why >> doesn't XMLUI set the `dspace.current.user.id` session cookie when >> running under Tomcat 8.5.x? How do I begin troubleshooting this? Otherwise, >> as far as I can tell, DSpace 5.8's XMLUI and JSPUI run fine under Tomcat >> 8.5.x. >> >> Thank you, >> >> On Thu, Jan 3, 2019 at 3:47 PM Alan Orth <alan.o...@gmail.com> wrote: >> >>> Hello, >>> >>> Our DSpace 5.8 instance has been running on Tomcat 7.0.x for a few years >>> now and I'm starting to test with Tomcat 8.5.x in preparation for moving to >>> a newer OS and application server stack. I seem to be having an issue with >>> user authentication and I'm not sure how to debug it. >>> >>> In our current production environment with Tomcat 7.0.x, when a user >>> logs into XMLUI a `dspace.current.user.id` session cookie is set. If >>> the user navigates to JSPUI they are still logged in. On Tomcat 8.5.x I >>> notice that I have to log in to XMLUI and JSPUI separately, and furthermore >>> no `dspace.current.user.id` is set. >>> >>> Can anyone help me understand what's going on? I'm testing the latest >>> binary releases of Tomcat 7.0.x an 8.5.x from Apache, with the same >>> application contexts and similar server.xml configurations. >>> -- >>> Alan Orth >>> alan.o...@gmail.com >>> https://picturingjordan.com >>> https://englishbulgaria.net >>> https://mjanja.ch >>> "In heaven all the interesting people are missing." ―Friedrich Nietzsche >>> >> >> >> -- >> Alan Orth >> alan.o...@gmail.com >> https://picturingjordan.com >> https://englishbulgaria.net >> https://mjanja.ch >> "In heaven all the interesting people are missing." ―Friedrich Nietzsche >> > > > -- > Alan Orth > alan.o...@gmail.com > https://picturingjordan.com > https://englishbulgaria.net > https://mjanja.ch > "In heaven all the interesting people are missing." ―Friedrich Nietzsche > > -- > All messages to this mailing list should adhere to the DuraSpace Code of > Conduct: https://duraspace.org/about/policies/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 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. > -- Tim Donohue Technical Lead for DSpace & DSpaceDirect DuraSpace.org | DSpace.org | DSpaceDirect.org -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/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 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.
