SESSION dbaac9e24c6e80bfcae429969a62383d(c): Authenticated converting from guest to JoeUser - default guest SESSION dbaac9e24c6e80bfcae429969a62383d(c): userLoggedIn called with JoeUser - undef SESSION dbaac9e24c6e80bfcae429969a62383d(c): Setting internal preference FOSWIKISTRIKEONE to da2e9241d90de64d7bc8adb71c3d6552 SESSION dbaac9e24c6e80bfcae429969a62383d(c): Setting internal preference REMEMBER to null SESSION dbaac9e24c6e80bfcae429969a62383d(c): Setting internal preference VALID_ACTIONS to HASH(0x2a576c0) SESSION dbaac9e24c6e80bfcae429969a62383d(c): Session is NOT authenticated SESSION dbaac9e24c6e80bfcae429969a62383d(c): = Initial user is guest SESSION dbaac9e24c6e80bfcae429969a62383d(c): userLoggedIn called with guest - undef SESSION dbaac9e24c6e80bfcae429969a62383d(c): Falling back to DEFAULT USER: guest SESSION dbaac9e24c6e80bfcae429969a62383d(c): No session, checking URI Params for a user SESSION ?(c): _loadCreateCGISession called. Here is a similar login on my local test system, with some annotation: I'll also edit and comment on your trace above. I have symlinked working/tmp from v1.1.9 to new installation and then tried to login with Google Chrome incognito window. I have tried that with Google Chrome and Microsoft Edge. I am sorry, but clearing out all cookie data didn't work. Thank you very much for your help, George! Then access your 2.1.3 system, without accessing the 1.1.9 system at all. Try clearing the all the domain cookies for your site. The same cookies and session-id were displayed in both the private window, and in the regular session. and then displayed the cookie information. I just tried logging into using a private window. I don't believe that Private Window is doing what you expect with regard to cookies, at least in Firefox. But the two sites each have unique working/tmp directories. With both Foswiki's using the hardcoded path of "/", the browser has a common cookie for both sites. The CGI Session file, saved in the working/tmp/cgisess_.The problem is that after successful authentication with Foswiki 2.1.3 - which I see in the logs only - immediately current page is rendered for guest user. Of course, I get logged out from one wiki when I log in to another one - that is expected and totally fine by me because the two wikis co-exist only until the upgrade is done, according to the official Foswiki docs. Sorry, I do not see how that might affect logging in from a private browser window - i.e. The work remaining is to convert to a different javascript library for interacting with the cookies, so that more flexibility is possible. The planned changes in Foswiki 2.2 are described in ConfigurableCookieNamesAndPaths. The LoginManager is TemplateLogin, and, but we are not yet ready to release Foswiki 2.2. | T13:59:02+03:00 info | alex | login | Main.WebHome | AUTHENTICATION SUCCESS - alex - Firefox | x.x.192.193 | | T13:57:54+03:00 info | admin | login | Main.WebHome | AUTHENTICATION SUCCESS - admin - Chrome | x.x.192.193 | This is how it looks like in the events log: There are no errors, but either the TemplateLogin form comes back, or a wiki page is rendered for guest user. I have also set the internal admin password in the configure interface.Īfter that, I cannot login to my new site. I have problems logging in to my new Foswiki installation after upgrade from version 1.1.9 to 2.1.3.Īs it is said in the UpgradeGuide, I have set up a new directory for the new version, extracted the distribution package, went through initial configure steps via web interface, and then copied over user and group pages and the. This question about Installation of Foswiki, Authentication or Authorisation: Task filed Cannot Login after upgrade from 1.1.9 to 2.1.3 Hello!
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |