beginnings of permission admin

I changed the table structure (again). It's a choice between two of
efficiency, integrity and no data duplication - I picked the last two.

We pass the permission regexps around as binaries and store them like
that too, just as we do for all other string-y datums.

I was toying with the idea of making set_permissions take a
#permission record instead of two separate regexp params, so that it
is easy to add more permissions later. But that is inconsistent with
the rest of the rabbit_access_control API, which is "flat", and
complicates the code in rabbit_control and the rabbit_tests.

1 files changed, 1 insertions, 0 deletions

diff --git a/ebin/rabbit_app.in b/ebin/rabbit_app.in
index e2f36c0f5f..77f9d299b7 100644
--- a/ebin/rabbit_app.in
+++ b/ebin/rabbit_app.in
@@ -17,4 +17,5 @@
          {default_user, <<"guest">>},
          {default_pass, <<"guest">>},
          {default_vhost, <<"/">>},
+         {default_permissions, [<<".*">>, <<".*">>]},
          {memory_alarms, auto}]}]}.