User Groups

This tutorial will only function if Discovery UI is set to use Passthrough credentials. I.E., the user's Discovery login information will also be used to authenticate to 3Sixty.

In this tutorial you will learn how to secure your Discovery's views for specific users groups in 3Sixty. The overall plan is to index a collection of files, and only allow certain user groups to see certain types of files.

1) Create the Elasticsearch connection

First, we need an Authentication Connection. Select Authentication under Connections, and click Create new Authentication Connection. We'll be using the default settings for Elastic (not authentication) in this case.

Select Integration under Connections and create an Elasticsearch connection for indexing, then, set the authentication connection.

2) Creating Filesystem connections

Creating a filesystem connection doesn't require an auth connections.

Repeat step 1), then under Connections, click Content Services and Create New Content Service Connection.

Set its type to Filesystem and set the Root Folder to location of the files to index.

3) Creating the user groups

In this case, we will have these users.

Now, we'll create our groups. Go to User Groups

We'll create a group of users who can only view PDFs and a group that can only view non-PDFs.

AND

If you don't see the user you want to add in the presented list, you can click SEARCH ALL USERS. You can multiselect from this menu.

4) Create the Indexing Jobs

Under the Integration menu, click List Jobs, then Create New Job. We'll assume there's a file system connection.

Set the content service connection (black), then make sure the start and end times are set (red). Files are picked up if their last modified date is between these times

Under tasks. Add a JavaScript task to skip non-PDFs files.

Now add a task to index user group information. Each document will receive a field that contains the listed user groups. Make sure to remember the index field.

Finally, add the content extraction task. Default values are fine

Add the following mapping in the mappings tab.

The Elasticsearch specification used can be seen below. Name the index whatever you wish.

Set the path to the location of the files to index (same as in the Content Service Connection)

In order to create the non-PDF indexing job, simply copy the job and update the JavaScript task !== to ===. This will skip PDFs. Also change the user group to index in the Index User Groups task to your non-PDFs group.

Now, run the jobs.

5) Search Connections

Now, we'll create the content search connections and set the security filters.

Now, we set the filter to use the field we indexed. 3Sixty will add the searching users ID to the search query, and only return results they can see.

You can also restrict this connection to a user group.

Users not in the selected groups will not be able to access Discovery Views using this connection or use this connection for searches.

Now, we'll see the connection to search the index we created.

6) Create the Content View

If you already know how to create a content view, you can skip this step. Any searches performed using the connection from Step 4 will be filtered or restricted based on the authenticated user.

Over in Discovery. We'll log in as a member of the non-PDFs group and confirm that you do not see any PDFs in your list of files.