rule/{rule-name}/action

Creates role-based access permissions (RBAC) associated with a role.

Resource URIs


URI	Description
<base_URI>/config/running/rule	Creates RBAC associated with a role.

Parameters

index: Specifies a numeric identifier for the rule.
action: Specifies whether the user is accepted or rejected while attempting to execute the specified command.
operation: Specifies the type of operation permitted.
role: Specifies the name of the role.
command: Specifies the command for which access is defined.

Usage Guidelines

GET, POST, PUT, PATCH, DELETE, OPTIONS, and HEAD operations are supported.

The switch obtains its configuration from the principal node. Enabling this feature solves most node-segmentation issues.

Examples

URI

The following example uses the GET option to retrieve the configuration details.

http://host:80/config/runnin/rule/5

None

<ruleurn:brocade.com:mgmt:brocade-aaa"" xmlns:y=""http://brocade.com/ns/rest"" y:self=""/rest/config/running/rule/5"">
  <index>5</index>
  <action>reject</action>
  <operation>read-write</operation>
  <role>testRole</role>
  <command y:self=""/rest/config/running/rule/5/command"">
    <show y:self=""/rest/config/running/rule/5/command/show"">
      <running-config y:self=""/rest/config/running/rule/5/command/show/running-config"">
      </running-config>
    </show>
  </command>
</rule>

The following example uses the PATCH option to modify the RBAC associated with a role.

http://host:80/rest/config/running/rule/5

<rule>
  <index>5</index>
  <action>reject</action>
  <operation>read-write</operation>
  <role>testRole</role>
</rule>

None

The following example uses the DELETE option to delete the RBAC associated with a role.

http://host:80/rest/config/running/rule/5

None

None