On Jun 25, 2008, at 6:36 AM, Raquel Cruz wrote:
Hi
So, do you have a solution to my problem? (Please, tell me yes...)
OK. "Yes" :)
I believe what you want is all of your guests to be able to edit pages
(I don't recommend doing this)
This is effectively like turning off security constraints on your portal
It appears that the "public-edit" constraint is not right for your
needs. Edit the page.security file, and change it from:
<security-constraints-def name="public-edit">
<security-constraint>
<roles>user</roles>
<permissions>view, edit</permissions>
</security-constraint>
</security-constraints-def>
to
<security-constraints-def name="public-edit">
<security-constraint>
<roles>user,guest</roles>
<permissions>view, edit</permissions>
</security-constraint>
</security-constraints-def>
Then change edit both /folder.metadata and /default-page.psml, change
from:
<security-constraints>
<security-constraints-ref>public-view</security-constraints-ref>
</security-constraints>
to
<security-constraints>
<security-constraints-ref>public-edit</security-constraints-ref>
</security-constraints>
btw, setting both public-view and public-edit makes no sense. The XSD
should allow only one definition
<js:security-constraint-ref>public-view</js:security-constraint-ref>
<js:security-constraint-ref>public-edit</js:security-constraint-ref>
So you should remove these entries and use the page constraints to
control your security until you have a better understanding of how
portlet-level constraints work
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
