The root config type for the Simple RBAC filter configuration file. This is the name of the header where the roles are passed in. This is the name of the header where the tenants are passed in. Mask rax-roles with NOT FOUND (404) and METHOD NOT ALLOWED (405) errors. By default rax-roles responds with a FORBIDDEN (403) if there is a role mismatch, if this is set to true, then the response will be NOT FOUND (404) if no methods are accessible or METHOD NOT ALLOWED (405) if some methods are available. If set to true, this filter will record, via JMX, the number of times each state in the generated state machine (the underlying mechanism) is accessed. These values may be used to determine api usage and coverage. dot output file for this validator DOT is a plain text graph description language. It is a simple way of describing graphs that both humans and computer programs can use. wadl output file for this validator WADL is the Web Application Description Language. It is a way of describing the API of a Web Application that both humans and computer programs can use. Whether or not you would like this filter to populate the delegation headers. Inclusion means you do. What quality you want any output headers to be. When setting up a chain of delegating filters the highest quality number will be the one that is eventually output. Default is 0.3 Sets the delegation component name for this validator. This is a list of resources, HTTP methods, and roles allowed to access them. The special HTTP methods ANY and ALL are shorthand for the four standard REST methods (GET, PUT, POST, DELETE). Others methods are supported, but they may must be explicitly stated. If a given Resource line has the HTTP method of ANY/ALL, then only the four are utilized. If more methods need to be supported by a particular Resource, then put them on another Resource line. The Simple RBAC resources can be either linked via an href attribute or defined directly in this element. Specifies a location to an external file which contains the Simple RBAC resources. If the message element has a value and the href attribute is configured, Response Messaging Service will use what is configured with href to send the message. If the file to which an href attribute of a message element is pointed is modified, Response Messaging Service will need to reload the configurations to guarantee that the changes will appear in the responses. Any changes to the config file itself will cause a configuration reload.