I have now tried the second option and it worked, however I had to activate the users as well as the changed roles. Before the users were activated, if I signed in as consultant I got both the Feature and Consultant pages in the menu as expected, however if I selected Colsultant and the Features, the Consultant entry was dropped from the menu and there were no messages in the logs.
Cheers Mike -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] Sent: 09 August 2005 10:21 To: [email protected] Subject: Re: [magnolia-user] RC3 - User not allowed to Read path [/] Thanks Philipp >From your comment, does this mean that if you use the address magnoliaPublic, you will be redirected to magnoliaPublic/.magnolia ? I tried magnoliaPublic/consultant as you suggest and I get the Features and Consultant pages as expected, however if I select Consultant from the menu, the Consultant page is displayed but the Feature menu has now disappear meaning that the Consultant user cannot get back to the feature pages. - should this happen ? I will try changing the role to / with deny Cheers Mike -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] Sent: 09 August 2005 10:05 To: [email protected] Subject: Re: [magnolia-user] RC3 - User not allowed to Read path [/] > Hello I am getting the 403 problem but it is not a permission issue > and it is not a partially completed bootstrap. OK > > I have set up a new page (called consultant) at the same level as > features and activated it. OK > > I then set up 2 roles, one called general with access to /features and > the other called consultant with access to /features and /consultant, > both these roles were activated. OK > > I then created 2 users - reader with role general and consultant with > role consultant - the two users were then activated. OK > > At this point if you point the browser at magnoliaPublic, both pages > are visible. OK > > I then logged into magnoliaPublic/.magnolia as superuser and changed > the config/server/secureUTIList/0001/URI to /* OK > Trying to access magnoliaPublic with a fresh browser brings up the > logon box, login in as reader causes a 403 error and the > magnolia-debug.log file contains the exception AccessDeniedException: > User not allowed to Read path [/] Two problems possible 1) you try to access magnoliaPublic/.magnolia. Since your roles has only access to /consultant and therefor they can not read the content of the root node. This leads to a 403 in the tree view since the tree starts reading in the root. Direct access to magnoliaPublic/consultant.html should work. 2) your code (template) needs access to the root (perhaps the menu or what ever). You can solve this giving the role read permission to / and subnodes. Then deny access to the restricted areas. hope this solves the problem. philipp > > I stoped and restarted Magnolia and tried again but got the same > result. > > Am I doing something wrong or should this work? Should work (I tried it) cheers philipp ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ---------------------------------------------------------------- ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ---------------------------------------------------------------- ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
