Secure a Web App Using Google Workspace (previously G Suite)
Enable SSO and Granular Access Control For A Header-Based Web App with Google Workspace
In this tutorial, we will use the Datawiza Access Proxy (DAP) to enable SSO and granular access control for a header-based web App. The IdP we will use is Google Workspace (previously G Suite). We will use DAP's side deployment mode, which means DAP and this app are running on the same server.
- The application will run on
- The DAP will run on
localhost:9772, which means the traffic to the app will reach DAP (running on port 9772) first and then be proxied to the application (running on port 3001).
- We will provide the docker images for the DAP and this header-based application.
Part I: Google Workspace Configuration
You will need to register a credential in Google API Console and get the following values for this credential:
- Client ID
- Client Secret
- (Optional) Service Account Credentials
- (Optional) Impersonate User
These values will later be used to set up Datawiza Access Proxy in Datawiza Cloud Management Console. Please follow IdP Configuration Guide: Google Workspace instructions on how to get those keys/values.
Part II: Create Application on Datawiza Cloud Management Console (DCMC)
You need to create an application and generate a keypair of (
PROVISIONING_SECRET) for this app on the DCMC.
Please follow Step2 : Datawiza Cloud Management Console to configure.
If you want to use user groups, you need to update the IdP config in DCMC: Upload the
Service Account Credentials which is the private key downloaded from the service account creation step above and input the
Part III: Run DAP With a Header-Based Application
You can use either Docker or Kubernetes to run DAP. The following is an example
docker-compose.yml file. You may need to login to our container registry to download the images of DAP and the header-based app. See Step3 : Configure DAP and SSO Integration for more details or Deploy DAP with Kubernetes for Kubernetes-specific instructions.
version: '3' services: datawiza-access-broker: image: registry.gitlab.com/datawiza/access-broker container_name: datawiza-access-broker restart: always ports: - "9772:9772" environment: PROVISIONING_KEY: ############################# PROVISIONING_SECRET: ############################# header-based-app: image: registry.gitlab.com/datawiza/header-based-app container_name: ab-demo-header-app restart: always ports: - "3001:3001"
docker-compose -f docker-compose.yml up, the header-based app should have SSO enabled with Google Workspace. Open a browser and type in
http://localhost:9772/. You should see the Google Workspace login page as follows.
Part IV: Pass User Attributes to the Header-Based App
The DAP gets user attributes from the IdP and can pass the user attributes to the application via header or cookie.
Please follow the instructions of Step4 : Pass User Attributes to pass the user attributes to the header-based app.
After successfully configuring the user attributes, you should see the green check sign for each of the user attributes as follows.
Part V: Achieve Granular Access Control
You can configure access control to an application based on user's attributes (e.g., given name, family name) and other metadata of a request (e.g., URL, IP, http method, access time).
Please reference Step5 : Achieve Granular Access Control for detailed instructions on how to set up access rules.
A Rule Example
- Create a user in Google Workspace, put the user in
- Create the following two rules:
hr pathcan only be accessed by
sales pathcan only be accessed by
- Verify that the user you created can only access
hrpage in the header-based app, but cannot access
salespage. Trying to access the header-based application on
localhost:9772in your browser, you should get something similar to the following screenshots.