(10.3.0-en) WAC Quickstart
This guide provides a simple walkthrough of how to use WAC, using the QueryPie homepage as an example.
Register the QueryPie homepage as a web app and add some sub-menus under Resources as URL paths.
Create a Policy and a Role that only allow access to these registered URL paths.
Assign this Role to the current user and verify the web app access control functionality.
Notification
This Quickstart guide is based on version 10.2.8
.
To follow this Quickstart, you need either Owner or Web App Admin privileges among QueryPie administrator permissions.
Admin-side
1. Registering a Web App
The substructure under /ko/resources on the QueryPie homepage (www.querypie.com) is as follows.
In this quickstart guide, we will register only some of these paths under the web app and then create a policy that allows access only to these registered paths.
/ko/resources/
├── discover/
│ ├── blog/ (Register)
│ ├── webinars/ (Register)
│ ├── white-paper/ (Register)
│ ├── certifications/
│ └── integrations/
│
└── learn/
├── documentation/ (Register)
├── tutorials/ (Register)
└── demo/
Navigate to the Admin > Web Apps > Connection Management > Web Apps menu.
Click the
Create a Web App
button to go to the web app registration page.
Enter the following information:
Name : QueryPie Web Site
Base URL :
www.querypie.com
또는10.10.10.10:443
Sub-paths (e.g., /ko) cannot be included in the Base URL.
It is recommended to exclude https:// when entering the Base URL.
Description: Enter a description for the web app (e.g., QueryPie Website).
Watermark: Select whether to apply a watermark to the user's browser screen when accessing the web app.
This helps prevent screen leakage by displaying information such as the accessor and access date/time on the browser when the web app is accessed.
This guide will assume it is set to On.
URL Paths: Enter sub-paths (Optional).
In this guide, we will enter sub-paths. Click the
+ Add Path
button to enter the sub-paths.
Path | Path Tag |
---|---|
|
|
|
|
|
|
|
|
|
|
|
|
Next, enter the remaining information.
User Activity Recording: Whether to record user activity.
Set to On and enable all options.
Excluded URL Paths is for entering paths to exclude from user activity recording. Leave this blank for now.
Tag: Tags for the web app. Leave this blank for now.
Click the
Save
button to save.
2. Registering a Policy
Next, we will create a policy for the QueryPie website that allows access only to the registered sub-paths.
Navigate to the Admin > Web Apps > Web App Access Control > Policies menu.
Click the
Create Policy
button and enter the following in the Create Policy modal:Name: QP Web Test Click the
Save
button to save.Click the newly created QP Web Test policy to enter its details page, then click the
Go to Editor Mode
button.Copy and paste the following content into the editor:
apiVersion: webApp.rbac.querypie.com/v1
kind: WacPolicy
spec:
allow:
resources:
- webApp: "QueryPie Web Site"
urlPaths:
- "/ko"
- "/ko/resources/discover/blog/*"
- "/ko/resources/discover/webinars/*"
- "/ko/resources/discover/white-paper/*"
- "/ko/resources/learn/documentation/*"
- "/ko/resources/learn/tutorials/*"
Click the
Save Changes
button, and then click theOK
button in the reason input modal to save.
3. Creating a Role
Now, we will create a new role and assign the policy created earlier.
Navigate to the Admin > Web Apps > Web App Access Control > Roles menu.
Click the
Create Role
button and enter the following:Name: QP Web Test
Click the newly created role to go to its details page > Policies tab. Click the
Assign Policies
button.In the Assign Policies modal, select the QP Web Test policy created earlier, click the
Assign
button to save, and close the modal.
4. Assigning the Role to a User/Group
Now, let's assign the newly created QP Web Test role to the current user.
Navigate to the Admin > Web Apps > Web App Access Control > Access Control menu.
Select the user or group to whom you want to assign the role.
For now, select yourself (the user performing this test).
On the user details page > Roles tab, click the
Grant Roles
button.In the Grant Roles modal, select the newly created QP Web Test role and click the
Grant
button to save.If the expiration date is not changed, it will be automatically set to one year from today.
Next, to verify that the access policy just created has been applied correctly, we will proceed with the user-side setup.
User-side
1. Installing the Root CA Certificate
While logged into QueryPie, click your profile button in the top right corner, and from the profile menu, click Support > Download Web Secure.
QueryPie > Profile MenuThe QueryPie Web Secure Download modal will open. Under A. Install Root CA Certificate, click the Download Link in Step 1. to download the certificate file.
QueryPie Web Secure DownloadFollow the Root CA Certificate Installation Guide to install the certificate and configure trust settings.
2. Downloading the Extension
From the QueryPie profile menu, click Support > Download Web Secure.
In the QueryPie Web Secure Download modal, under B. Install Chrome Extension > Step 1., click the Download Link to download the Extension file.
3. Installing the Extension and Configuring the Host
In the Chrome address bar, enter chrome://extensions/.
Enable the Developer mode toggle in the upper right corner of the page.
Drag and drop the downloaded Extension file (without unzipping it) into the extensions area.
Chrome > Managing ExtensionsThe Host Configuration page will open in a new tab. Paste your current QueryPie address into the QueryPie Host field and click the
Continue
button.If the Host information is valid, a
Go to Dashboard
button will appear. Click it to open QueryPie in a new tab.Host Configuration Page
Warning
Management is not guaranteed for tabs that were open before installing the WAC extension. There may be issues with access policy enforcement and audit logging.
Please close all existing browser tabs and windows before installing the extension.
4. Accessing the Web App via QueryPie
Click the
Go to Dashboard
button. A new tab will open, displaying the QueryPie Web console.If you are currently logged into QueryPie, the Web App Dashboard will open.
If you are not logged in, you will be redirected to the login page. After logging in, click Web Apps in the top menu to access the dashboard.
If the Role selection modal appears, select QP Web Test.
In the Web App Dashboard, under My Apps, you will see the QueryPie Web Site app icon that you registered earlier. Click the icon to access the website.
QueryPie > Web Apps > Web App DashboardUpon first access, a screen will inform you that the current web session is being recorded. Click the
Continue
button to proceed to the website.Web Session Monitoring NotificationYou can see that the Watermark is applied to the QueryPie homepage.
If you attempt to access a non-allowed page (e.g., the Products menu), you will be redirected to a blocking notification screen.
QueryPie Access Denied
Admin-side (again)
1. Checking Web App Access History
Navigate to Admin > Audit > Web Apps > Web Access History.
You can view the access history for web apps accessed by the current user.
Action Type: The start and end of web app access.
Connect: Access started.
Displayed when the web app is accessed. All sub-paths are recorded separately.
Disconnect: Access ended.
Displayed when a tab is closed or the user navigates to another page.
Result: Outcome.
Success: Access successful.
Failure: Access failed.
Displayed as access failed if blocked by a WAC policy.
2. Checking User Session Recordings
All records of the user accessing the controlled web app and navigating its sub-pages are displayed, based on the web app and role.
Recordings are only kept if User Activity Recording was enabled when the Web App was created.
Navigate to Admin > Audit > Web Apps > User Activity Recording.
Click on a record associated with the current user's name to go to the details page.
In the Event Timeline, you can see the user's activities in chronological order.
Click the filter to view activities by type.
Searchable values are as follows:
Content (clicked text or link)
URL (URL of the page being accessed)
Tab ID (ID of the tab used)
Screenshots of the page the user was actually viewing are captured for each event.