> Authenticated pages must have auth property set on. > It may sense to > redesign your application so that it has two trees > actually: one > non-authenticated and second with authentication > enabled. So users will > come to the first one and browse pages as is but if > page code sees > appropriate cookies it does redirect to > authenticated tree (for example, > foo.mysite.com/dir1/ redirects to > foo/mysite/auth/dir1 where page /auth/ is > active (mirrors /dir1/ by loading and executing > original /dir1/ code) and auth-enabled).
I kind of played with the idea already to have a separate authentication-requiring host for that, i.e. admin.mysite.com next to the freely accessible www.mysite.com. Both share the same root page, where the authenticated property is set to "inherited", so the root page when called at admin.mysite.com/ requires authentication, when accessed via www.mysite.com/ it doesn't. However, in order to test this idea I made the authentication required for an arbitrary page in my site, and that didn't work: even after having logged in at this separate login page, and after having checked the MidgardLogin cookie was set, I still got the authentication popup. Am I overseeing something? pascal __________________________________________________ Do You Yahoo!? Yahoo! Games - play chess, backgammon, pool and more http://games.yahoo.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
