Bugzilla – Bug 930591
If Guest has rights to see the Default Home Page, they are directed there if there is no Default Guest Home Page defined
Last modified: 2015-06-15 21:11:06 UTC
+++ This bug was initially created as a clone of Bug #925281 +++ Actual: If Guest has rights to see the Default Home Page, they are directed there if there is no Default Guest Home Page defined. Expected: Regardless of Guest's rights to the Default Home Page, they should never be directed there by default.
There's just one important thing: The guest access is _disabled_ (!) on the sites where we experience that problem. If guest acces would be enabled then I would agree that it's not such a big problem. Thanks!
Marked NeedInfo to Erik. Please provide more complete steps to dup. If I have Guest disabled, it ALWAYS goes to the login dialog and I never see the Default Home Page. How are you doing this with Guest disabled? Is this because the upgrade incorrectly ENABLED guest? (Bug#925281) If, after the upgrade you've made SURE that Guest is disabled AND you still see this, I'd like more complete steps as to how to set this up. The ONLY way I can dup this is taking advantage of bug#925281 where Guest incorrectly gets enabled after the upgrade. With Guest being enabled and having rights to the Default Home Page, yes, they see it in that case.
Hi Dennis, just follow the exact steps mentioned by Monika in comment 3 in https://bugzilla.novell.com/show_bug.cgi?id=925281#c3 : Steps to reproduce: 1. do _not_ allow Guest Access (in the Web Application Configuration)! 2. set the Default Home Page to the root of the system, normally "Home" (+ Guest does not have/need rights to the "Home" WS!) This is reproducable on systems that got upgraded from 3.4 but also on clean and fresh 4.0 installations.
Changed Priority to P1, Severity to Major and the Target Milestone to 4.0.1. Also added FTF keyword. I can finally dup this, although I don't know why I can't on my development machine, only on a full production installation. I believe the problem was introduced with the fix for bug#768914. The fix for that was a little too aggressive in redirecting to the Default Home Page and was doing so in cases where it shouldn't have been (e.g., the case described by this bug.) I'm still trying to understand if this bug is related or causing to bug#925281.
The fix for this has been checked into the Vibe 4.0.1 code base. ssf (4.0.1) revision: 22617 and 22618 - - - - - I'm holding off marking the bug fixed until the CCB rules on the FTF request. The fix is ready to be checked into the Vibe Hudson FTF code base as well.
This fix is in the Vibe OnPrem Filr 1.3.0 build 20150515201342. open source project revision 22619, and closed source project revision 7822.
*** Bug 925281 has been marked as a duplicate of this bug. ***
Marked Resolved/Fixed. The fix for this has now been checked into the Vibe Hudson FTF code branch. ssf revision: 22635 - - - - - In order to apply this fix to a Vibe Hudson installation, you'll need to copy the following: - kablink-teaming-main.jar
This fix is in the Vibe OnPrem 4.0.0 build 20150522163952. open source project revision 22635, and closed source project revision 7827.
Build 518 exhibited the problem Build 528 has the fix and does not display the home page to a disabled guest