XNAT 1.7.2 : redirection issue on first login
MarkC
MarkC
Zihao ZHU
在 2017年2月28日星期二 UTC+8下午10:59:57，MarkC写道：
Herrick, Rick
There was a bug in the security layer where the app context somehow got dropped when checking whether pages were part of the setup. Basically, during initialization, the app would redirect you to http://server/xnat/setup, then check to see whether that was a page you’re allowed to go to before the system was initialized. The problem is that it would test /xnat/setup against /setup and say nope, that’s not a valid page, you need to go to… /xnat/setup. Thus the loop. I’m not sure what changed to make this stop working, but I pushed a fix for the issue up last week. The next release of XNAT should work properly with a non-root context path.
--
Rick Herrick
Sr. Programmer/Analyst
Neuroinformatics Research Group
Washington University School of Medicine
--
You received this message because you are subscribed to the Google Groups "xnat_discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
xnat_discussi...@googlegroups.com.
To post to this group, send email to
xnat_di...@googlegroups.com.
Visit this group at https://groups.google.com/group/xnat_discussion.
For more options, visit https://groups.google.com/d/optout.
The materials in this message are private and may contain Protected Healthcare Information or other information of a sensitive nature. If you are not the intended recipient, be advised that any unauthorized use, disclosure, copying or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error, please immediately notify the sender via telephone or return mail.
Albert Crowley
Herrick, Rick
Yes, committed 3 March:
· https://bitbucket.org/xnatdev/xnat-web/commits/c01023e48b7d3be27c7c557e4e2be7e5730f42ca
· https://bitbucket.org/xnatdev/xnat-web/commits/84febbcb6d669389294f4b5a049a9af161db71ca
The relevant issues are XNAT-4758 and XNAT-4759. If you run into any other issues related to this, feel free to add a comment on the issue with any details.
--
Rick Herrick
Sr. Programmer/Analyst
Neuroinformatics Research Group
Washington University School of Medicine
Raminder Singh
On Tuesday, March 7, 2017 at 11:21:20 AM UTC-5, Rick Herrick wrote:
Raminder Singh
Herrick, Rick
Raminder,
The issues that Mark and others had previously were specifically because of the application context, that is, the part of the URL after the server address, e.g. the highlighted part here https://foo.school.edu/xnat. Since you have yours installed as ROOT.war, I think you’re seeing a different issue. You shouldn’t need to modify the conf/context.xml in your Tomcat configuration other than to uncomment the <Manager> element (setting pathname=”” there gets around a serialization error message on start-up).
Application mapping in XNAT 1.7 is best handled by the Tomcat deployment logic, i.e. if you put your ROOT.war into the Tomcat webapps folder, you’ll get XNAT running at http://server, otherwise if you put xnat.war or foo.war or whatever into the webapps folder you’ll get http://server/xnat, http://server/foo, etc.
Try restoring the server.xml and context.xml files for Tomcat to their default state other than the <Manager> element in context.xml (this may mean *changing* the server.xml back to the default state if you had it modified for an XNAT installation).
The other possibility is that you have SSL being handled by a front-end proxy like Apache or nginx, but have the security channel (on the Site Administration page under Site Settings->Security->Security Channel) set to https. The problem in that case is that, since the proxy handles SSL, the request arrives at Tomcat as http. But then XNAT’s security layer sees that, realizes the request is http, and redirects the request back to https. So then the browser gets that back and requests https://server, which goes through the proxy, which sends the request onto Tomcat as http, and XNAT does a redirect to https and so on. There’s no solution to this particular problem on the XNAT side: whatever happens to the request before it arrives at Tomcat is beyond its control, so the option in that case is to leave the security channel set to http or Any.
--
Rick Herrick
Sr. Programmer/Analyst
Neuroinformatics Research Group
Washington University School of Medicine
From:
"xnat_di...@googlegroups.com" <xnat_di...@googlegroups.com> on behalf of Raminder Singh <rsan...@gmail.com>
Reply-To: "xnat_di...@googlegroups.com" <xnat_di...@googlegroups.com>
Date: Thursday, March 30, 2017 at 1:14 PM
To: "xnat_di...@googlegroups.com" <xnat_di...@googlegroups.com>
Subject: [XNAT Discussion] Re: XNAT 1.7.2 : redirection issue on first login
I tried to change conf/context.xml and still no luck to resolve ERR_TOO_MANY_REDIRECTS. I verified permissions for xnat user and it all look good. Please advice me what else I can try.
--
You received this message because you are subscribed to the Google Groups "xnat_discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
xnat_discussi...@googlegroups.com.
To post to this group, send email to
xnat_di...@googlegroups.com.
Visit this group at https://groups.google.com/group/xnat_discussion.
For more options, visit https://groups.google.com/d/optout.
Raminder Singh
legacy....@gmail.com
Herrick, Rick
Yes, you’d still have this issue with 1.7.2, which was released on 10 January. The fixes for this were committed in March. I’m in the process of building the release war for 1.7.3 at this very moment. You should be able to grab that later today or tomorrow. Try with that and see how it goes.
--
Rick Herrick
Sr. Programmer/Analyst
Neuroinformatics Research Group
Washington University School of Medicine
Phone: +1 (314) 273-1645