[asterisk-dev] [Code Review] Manager consumption test for ACLs

[opticron]

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/2047/#review6692
-----------------------------------------------------------

Ship it!


- opticron


On July 13, 2012, 4:48 p.m., jrose wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviewboard.asterisk.org/r/2047/
> -----------------------------------------------------------
> 
> (Updated July 13, 2012, 4:48 p.m.)
> 
> 
> Review request for Asterisk Developers, Mark Michelson, opticron, and Matt Jordan.
> 
> 
> Summary
> -------
> 
> The test involves configurations of acl.conf and manager.conf working in tandem. It can be sumarized into 4 tests currently and new tests can be added rather easily.
> 
> All manager users are tested against the following addresses:
> 127.0.0.1
> 127.0.0.2
> 127.0.0.3
> 127.0.0.4
> 
> test1 - An ACL specified within manger.conf using permit/deny only
> The ACL is written in such a way that it will only work on address 127.0.0.1
> 
> test2 - The same ACL is used, but the manager user refers to it with acl=[aclname] instead of by manually defining it.
> 
> test3 - 3 named ACLs are used. The first denies only 127.0.0.1, the second denies only 127.0.0.3, and the third denies only 127.0.0.4
> Collectively, only 127.0.0.2 is accepted.
> 
> test4 - A named ACL is used. The named ACL is not defined in acl.conf, so it is an invalid ACL and all addresses are rejected for
> the user.
> 
> Like most tests I write, I imagine this one will have to be revised.
> 
> 
> Diffs
> -----
> 
>   /asterisk/trunk/tests/manager/acl-login/configs/ast1/acl.conf PRE-CREATION 
>   /asterisk/trunk/tests/manager/acl-login/configs/ast1/manager.conf PRE-CREATION 
>   /asterisk/trunk/tests/manager/acl-login/run-test PRE-CREATION 
>   /asterisk/trunk/tests/manager/acl-login/test-config.yaml PRE-CREATION 
>   /asterisk/trunk/tests/manager/tests.yaml 3318 
> 
> Diff: https://reviewboard.asterisk.org/r/2047/diff
> 
> 
> Testing
> -------
> 
> The test was ran with diagnostic logs to make sure the right ACLs were passing.
> 
> Also, the expectations were changed around to make sure that failures that were anticipated to be allowed would result in test failure and succeses that were anticipated to not be allowed would also result in failures.  In each case, the results changed as expected.
> 
> Lastly, the ACL rules were changed for much of the same reason.  In each case, the results changed as expected.
> 
> 
> Thanks,
> 
> jrose
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20120717/14c5b138/attachment-0001.htm>