Please use either support, if you are a customer, or our very active and helpful user list to discuss this kind of matters as this list is intended to discuss the development of Magnolia itself.
As far your question goes, I think it might be a caching issue (browser, proxy, ....), but the customization might have its influence on that too. Can you check the HTTP headers when the login form is returned to ensure that there the page is not cacheable (Cache-Control, ...) Cheers - Philipp On 08.03.2011, at 17:41, Erik Alphenaar wrote: > > As the subject suggests: > The Magnolia login screen appears on public instance that is accessible for > the anonymous user, but is gone after refresh. It feels random, but in these > cases it usually is not, but let's say I cannot find a pattern yet. > > Additional info: > > We have created an additional jaas realm with a separate usermanager config > and a custom JCRAuthenticationModule implementation of the init method that > uses a users' email address as the login name. > Could this be of any influence? > Or could this be related to a cache issue? > > Any help or thoughts are greatly appreciated. > > > Rgds, > > Erik Alphenaar. > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
