Chapril/xmpp.chapril.org-ejabberd
25
1
Fork 0
mirror of https://github.com/processone/ejabberd.git synced 2024-11-22 16:20:52 +01:00
Code Releases Activity

Add explanation about global Access precendence over vhost Access (EJAB-803)

Browse Source 
SVN Revision: 2824
This commit is contained in:
Badlop 2009-12-23 16:08:34 +00:00
parent c7f4f39c03
commit 71142e336d
2 changed files with 9 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
doc/guide.html
View File

@ -1183,7 +1183,10 @@ The syntax is:
sequentially checks if that JID matches any of the ACLs that are named in the
second elements of the tuples in the list. If it matches, the first element of
the first matched tuple is returned, otherwise the value &#X2018;<TT>deny</TT>&#X2019; is
returned.</P><P>Example:
returned.</P><P>If you define specific Access rights in a virtual host,
remember that the globally defined Access rights have precedence over those.
This means that, in case of conflict, the Access granted or denied in the global server is used
and the Access of a virtual host doesn&#X2019;t have effect.</P><P>Example:
</P><PRE CLASS="verbatim">{access, configure, [{allow, admin}]}.
{access, something, [{deny, badmans},
{allow, all}]}.

5
doc/guide.tex
View File

@ -1439,6 +1439,11 @@ second elements of the tuples in the list. If it matches, the first element of
the first matched tuple is returned, otherwise the value `\term{deny}' is
returned.
If you define specific Access rights in a virtual host,
remember that the globally defined Access rights have precedence over those.
This means that, in case of conflict, the Access granted or denied in the global server is used
and the Access of a virtual host doesn't have effect.
Example:
\begin{verbatim}
{access, configure, [{allow, admin}]}.