In addition to providing access to security information within the web application code, the security system of the platform provides access to security information within action sequences. The information then can be used in JavaScript rules, presented in reporting prompts, provided as input to SQL Lookup Rules, etc.
If you look at the inputs section of an action sequence, you will see inputs typically defined like this:
| Code Block | ||||
|---|---|---|---|---|
| ||||
<inputs>
<someInput type="string">
<sources>
<request>someInput</request>
</sources>
</someInput>
</inputs>
|
In the above example, the input (called someInput) can be found by looking at the request (HttpServletRequest, PortletRequest, etc.) for a variable called someInput. Then, throughout the rest of the action sequence, specific actions can reference that input.
Security Inputs
Pentaho BI Platform extends the inputs to provide a unique type of input--the security input. This input (as of this writing) supports the following input names:
Input Name | Type | Description |
|---|---|---|
| | The name of the currently authenticated user. |
| | The roles that the currently authenticated user is a member of. |
| | |
| | |
| | All the known roles in the system. Use caution since this list could be quite long. |
| | All the users known to the system. Use caution since this list could be quite long. |
Example
The following input section will get the list of the user's roles, and make it available to all the actions in the action sequence:
| Code Block | ||||
|---|---|---|---|---|
| ||||
<inputs>
<principalRoles type="string-list">
<sources>
<security>principalRoles</security>
</sources>
</principalRoles>
</inputs>
|