Well, now you know why JavaDoc is not enough for documentation... Gesendet mit BlackBerry
-----Original Message----- From: Mark Struberg <[email protected]> Date: Tue, 28 May 2013 15:12:02 To: [email protected]<[email protected]> Reply-To: [email protected] Subject: Re: DS + mfRid/windowdId + Shiro UserFilter/redirectToLogin = infinite redirect loop in browser Hi Just provide a ClientWindowConfig impl which sets the ClientWindowRenderMode to NONE. I've recently posted code samples how to do so. LieGrue, strub ----- Original Message ----- > From: titou10 titou10 <[email protected]> > To: [email protected] > Cc: > Sent: Tuesday, 28 May 2013, 16:02 > Subject: DS + mfRid/windowdId + Shiro UserFilter/redirectToLogin = infinite redirect loop in browser > > Hi, > With the current snapshot of DS, we have a problem with Shiro and the > introduction of the mfRid/windowdId parameters > Shiro is configured to redirect to the login page (defines in > shiro.ini) if required > > We use an AJAX compatible Shiro UserFilter as explained here : > http://balusc.blogspot.ca/2013/01/apache-shiro-is-it-ready-for-java-ee-6.html > > When this happens, the browser enter an infinite redirect loop, > because, I *guess* it's because Shiro does not include the > mfRid/windowdId parameters on the login page > Q: > - Am I right? > - Is it possible to exclude some pages (like the login or error pages) > from being in need of having those parameters > - Maybe it's possible to "add" those parameters in our login > pages? > > It would be a real pain to override a *lot* of Shiro classes to handle > the mfRid/windowdId parameters everywhere > > At this time we can not test/use the current code of DS with our apps. > > WDYT? >
