org.apache.karaf.command.acl.system.cfg 2.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354
  1. ################################################################################
  2. #
  3. # Licensed to the Apache Software Foundation (ASF) under one or more
  4. # contributor license agreements. See the NOTICE file distributed with
  5. # this work for additional information regarding copyright ownership.
  6. # The ASF licenses this file to You under the Apache License, Version 2.0
  7. # (the "License"); you may not use this file except in compliance with
  8. # the License. You may obtain a copy of the License at
  9. #
  10. # http://www.apache.org/licenses/LICENSE-2.0
  11. #
  12. # Unless required by applicable law or agreed to in writing, software
  13. # distributed under the License is distributed on an "AS IS" BASIS,
  14. # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  15. # See the License for the specific language governing permissions and
  16. # limitations under the License.
  17. #
  18. ################################################################################
  19. #
  20. # This configuration file defines the ACLs for commands in the system subshell
  21. #
  22. # The format of this file is as follows:
  23. # The name of the file corresponds to a Configuration Admin PID. This file is for PID:
  24. # org.apache.karaf.command.acl.system
  25. # The prefix org.apache.karaf.command.acl. determines that this file defines ACLs for karaf
  26. # commands. The last word on the PID declares the scope that it applies to, i.e. this file
  27. # is for the 'system' scope.
  28. # Entries in this file map to commands within the defined scope. The simplest role definition
  29. # has the form:
  30. # command = role1, role2, role3
  31. # Specific roles can also be declared for certain arguments to the command. This is done using
  32. # regular expression matching.
  33. # All the arguments to the command are represented as a list using the following syntax:
  34. # [arg1,arg2,arg3]
  35. # The matching is done after converting this list into a string. So the line
  36. # start-level[/.*[0-9][0-9][0-9]+.*/] = manager
  37. # declares that a manager role is needed to set a start level with 3 digits or more. The .*
  38. # wildcards at the beginning and end are used to match the '[' and ']' characters surrounding.
  39. # When looking for a match the regular-expression based ACLs are always checked first. If any
  40. # of them match the associated roles are used.
  41. #
  42. # If no match can be found based on reg-exp ACLs, a match is looked for based purely on the
  43. # command name.
  44. #
  45. # If no command-name match can be found it is assumed that the command does not need a specific
  46. # role and can therefore be invoked by any user.
  47. property = admin
  48. shutdown = admin
  49. start-level[/.*[0-9][0-9][0-9]+.*/] = manager # manager can set startlevels above 100
  50. start-level[/[^0-9]*/] = viewer # viewer can obtain the current start level
  51. start-level = admin # admin can set any start level, including < 100