Dear John,
Ok, I tried out the following:
webconfig authorization set as:
<authentication mode="Windows" />
<authorization>
<deny users="?" />
</authorization>
My namespace definition is set as:
AllowRead: authenticated, anonymous
AllowManageNamespace: authenticated
My topic definition is set as:
DenyEdit: all
AllowEdit: domainname\Wilson.CHC, Wilson.CHC
And I was not given the permission to edit the page. Is it because of the
windows authentication? Would a forms authentication work better? Thanks in
advance for all the time taken to answer my questions, I hope I'm not being
a bother :-)
Regards,
Wilson
P.S I put both versions of my domain login (with and without domain) because
I didn't know which to follow :-)
_____
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of John
Davidson
Sent: Sunday, February 03, 2008 12:06 PM
To: FlexWiki Users Mailing List
Subject: Re: [Flexwiki-users] Allow/Deny Editing Topics
No. The section Evaluation Model in the reference [1] explains it best. It
would have been possible to reverse the statements so that it was
DenyEdit: all
AllowEdit: Wilson
would also work. The key is it evaluates the rules in order and looks to see
if, after evaluating all rules, the user has the right. If your last rule is
a DenyEdit:all then no user will ever have edit rights.
John Davidson
[1] http://www.flexwiki.com/default.aspx/FlexWiki/FlexWikiAuthorization.html
On Feb 2, 2008 9:11 PM, Wilson Chuah <[EMAIL PROTECTED]> wrote:
Dear John,
Thanks for the speedy reply. So Deny always takes precedence over Allow
right? Ok, I know how to proceed now. Thanks again
Regards,
Wilson
_____
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of John
Davidson
Sent: Saturday, February 02, 2008 10:18 PM
To: FlexWiki Users Mailing List
Subject: Re: [Flexwiki-users] Allow/Deny Editing Topics
It would not quite work the way you want it to.
The DenyEdit: all would override the AllowEdit:Wilson.
What I believe you should do is
AllowRead: all
AllowEdit: Wilson
It is also good in a testing system to ensure that your admin has a
ManageNamespace permission, as that will allow corrections to be made when
setting permissions in topics.
Another option would be to use topic locking and allow Wilson to Lock/Unlock
topics.
John Davidson
On Feb 2, 2008 3:12 AM, Wilson Chuah <[EMAIL PROTECTED]> wrote:
Hi All,
I've been reading
http://www.flexwiki.com/default.aspx/FlexWiki/FlexWikiAuthorization.html and
before I start configuring, can I ask if DenyEdit takes precedence over
AllowEdit? Example:
AllowEdit: Wilson
DenyEdit: all
Would the above authorization allow Wilson to configure the topics while
denying everyone?
Regards,
Wilson Chuah
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Flexwiki-users mailing list
Flexwiki-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flexwiki-users
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Flexwiki-users mailing list
Flexwiki-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flexwiki-users
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Flexwiki-users mailing list
Flexwiki-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flexwiki-users
