This documentation is for WSO2 Application Server version 5.0.0. View documentation for the latest release.

Role-Based Content Filtering

The 'data service hosting' feature facilitates controlling access to sensitive data for specific users roles. This facility is Role-based content filtering. It filters data where specific data sections are only accessible by a given type of users.

For information on adding and managing user and roles, refer to section "User Management."   

Follow the instructions below to filter a data service according to a specific user role.

 1. Log on to the product's management console and select  "Services -> List" under the "Main" menu.

2. The Deployed Services page appears which lists out all the currently active services and service groups.

Click on the data service you want to edit.

3. The dashboard of the data service opens. Click on the Edit Data Service link. In this example, we edit using the management console.

4. Navigate to the Queries page of the data service, select the query you want to edit and click on Edit Query.

For more information on editing a data service, refer to page "Create a Data Service Using Various Data Sources" in section "Data Service Management -> Deploying Data Services."

5. The Edit Query page opens. For example,

6. In Output Mappings, edit the field which needs to be filtered and tick the appropriate user role in the Allowed User Roles section.

7. Once all the required roles are set, the result entries of the Edit Query page look as follows in this example,

8. Next, security and an authentication mechanism must be enabled in the service in order to identify users sending requests.

Click security in the service's dashboard and enable it. Also select the type of authentication under the 'Basic Scenarios' section.

9. Click next. The Activating Security window opens. It displays the user groups available. Select the needed user group to allow access to the service.

For more information on service-level security and step-by-step instructions on enabling it, refer to section "Service Management -> Service-Level Security Implementation ."