Getting Started : Going Further with CloudView : Securing Document Access
 
Securing Document Access
 
How Document Security Works
Tutorial: Implement Document Security
Security in Exalead CloudView has different levels:
Document-level security ensures that documents which users are authorized to view are displayed as search results from the Exalead CloudView index.
Application-level security ensures a restricted access to features in the Administration Console and Business Console.
This section focuses on applying document-level security.
For more information, see "Managing User Access" in the Exalead CloudView Administration Guide .
How Document Security Works
Tutorial: Implement Document Security
How Document Security Works
Document security is implemented by indexing a document's Access Control List (ACL) and generating security tokens when the user authenticates.
If your network already has a security policy in place, you may want to reuse it for authentication in Exalead CloudView.
Note: In Exalead CloudView, password, and login management is centralized and changes are automatically propagated.
Configure a security source to authenticate users and authorize their document access.
The document security workflow is described below.
Step
Description
1
The user logs in to the Exalead CloudView search application.
2
Exalead CloudView queries a security source for:
Authentication: to verify the user's login and password
Authorization: to verify the security tokens for the user and the group to which the user belongs
3
The user enters his search query.
4
The user's query and security tokens are sent to the index.
The index only fetches documents that match both the user's query and the user's security tokens.
Tutorial: Implement Document Security
As already stated, Exalead CloudView queries a security source for:
Authentication: to verify the user's login and password
Authorization: to verify the security tokens for the user and the group to which the user belongs
This section will show how to configure user authentication only.
Create the Security Source
1. In the Administration Console, go to Search > Security Sources and click Add security source.
a. For Name, type MySecurity.
b. For Type, select Simple Security.
2. For this security source, under Config > Users:
a. Click Add item to add a new user.
b. Specify user login information: Login: myuser, Password: myuser, Display name (the name that will be displayed when the user is authenticated): myuser
3. Click Apply.
4. Under Test user authentication:
a. Click Test.
b. Enter the user Login and Password, and click Test.
If successful, your user ID, display name, and full list of security tokens (if any) displays.
If not, check your parameters and contact your system administrator.
Enable Security in the Search Application
We now have a security source which can be queried to check logins. We now need to enable security in the UI, and tell it to use the security source we just created.
1. In Mashup Builder, select Application from the top left menu bar.
2. Under General > Security, click Add a security provider.
3. In the Add security provider dialog box, select CloudView Security Provider and click OK.
Note:  
A login page is created in your application.
4. In the Source field, select the security source you created in the previous procedure, for example MySecurity.
5. In the Mashup pages section, select the pages of your application on which you want to enable security. For example, the index and search pages.
6. For each page on which security is enabled, also add the Logout widget:
a. Display the search page.
b. In Widgets, search for ‘Logout’.
c. Drag the Logout widget to the page.
d. Repeat these steps for the index page.
7. Click Apply to save the configuration changes.
Test Authentication
1. Go to the Mashup UI.
You are prompted to log in.
2. Log in with the login/password defined previously (myuser).
Once logged in, you can see the logout widget on the page (if you added the Logout widget).