Accessing Mattermost with Browzer


This guide is a walk through to setup a BrowZer application to access Mattermost. 

To learn more about BrowZer see Getting started with BrowZer


  • A Cloud Ziti Network up and running.
  • Having a Mattermost instance up and running with an edge router that has network access. Please follow Appendix instructions to install Mattermost(preview) if you don't already have a Mattermost instance up and running.  Please note the Mattermost preview is not an production instance, when using a production setup the ER will be separate from the Mattermost instance.  If you need instructions on how to deploy Mattermost, please review their documentation here.



Part 1: Setup Needed Items to support a BrowZer Application

In this section:

In the Console, Create a NetFoundry Hosted Edge Router with the WSS Listener enable. BrowZer requires at least one Edge Router with the WSS Listener enabled.  Launching a NF Hosted is recommended. 

In the Console, Create an Edge Router Policy to make ensure this router is available for your Identities(Endpoints).


In the Console, Create the Service you want to access Mattermost.  We recommend using an Advance Service.  For the FORWARD ADDRESS, use the container name "mattermost" or the container's IP address.  The FORWARD PORT should be 8065.


In the Console, Create a Service Policy(AppWan) to allow the access to the specified clients we’ll create later.

Part 2: Auth0 & JWT Signer

In this section:

This tutorial follows the Auth0 settings. Other IDP must have their own settings. If you don't already have an account you can sign up for a free account at

Adding a new Application in Auth0

Once you have an account setup you can add a new "Application":



Then click on the "Create Application":


Then Create a "Single Page Web Application":



Gathering Information from Auth0

In order to setup the new JWT Signer we'll need to get some information from the new Auth0 Application that was just created.


From the Application we’ll require a few things we’ll need to write down. From the basic Information we’ll gather the “Domain” and “ClientID

Scroll down to the Advanced Settings and click on Endpoints

You’ll also need to write down the OAuth Token URL that will be used on the BrowZer App creation and the JSON Web Key Set.



Adding the callback & logout URL to your BrowZer App(s) you created

All BrowZer Apps have the following template:



  • APP_NAME, is the name we’ll assign to the BrowZer app we’ll create.
  • NET_NAME, is the name we’ll assign the first time you click on “BrowZer Apps”.

In Auth0, under the Application/Settings you'll find "Allowed Callback URLs" & "Allowed Logout URLs"

You can add one callback URL for all apps are created under the same NET_NAME In this case, NET_NAME=natashell.  The URL needs to be in this format: https://*.<NET_NAME>

For example:


For Example:



Adding a JWT Signer & Authentication Policy

Create the JWT

In the Console, Create a new JWT Signer

Using the values from Auth0 fill out the information in the new JWT Signer dialog.

For the ISSUER, use the “Domain” value.


(Please make sure to add the trailing slash).

For the Audience, use the “ClientID” value.

For the JWKS Endpoint, use the "JSON Web Key Set URL" value.

For the External Auth URL, use the "OAUTH Token URL" value.

Finally set the JWT Claim "email" & the Identities to "External Id".



Create the Authentication Policy

In the Console, Create a new Authentication Policy

In this example we disable the certificate options & only use the JWT Signer as the Authenticator.



Create or Assign Identities(Endpoints) to the Authentication Policy

In the Console, Create or update the Identities(Endpoints) that will have the access to BrowZer. Please ensure you have add the necessary attributes you define in your Service Policy(AppWan) to the Identities(Endpoints) so it’ll have access to the service.

Finally make sure it has an Authentication Policy you created for BrowZer


Part 3: The BrowZer Application

In this section:

Make sure to complete the BrowZer Getting Started by clicking on the BrowZer Apps in the navigation menu.

Create a BrowZer Application

In the MOP Console, Create a new BrowZer Application.

For the App Entry, Select the service you created on Part 1.

For the Public URL, you’ll set a name for your app (APP_NAME), this name creates the whole URL you’ll use to access your service securely. In this case, APP_NAME=app and the URL is

For example:

Set the OIDC Base URL to the “Domain” value from Auth0 in Part2, in the format:


(This time without any slash at the end)

Set the ClientID to the "ClientId" value you got from Auth0 in Part 2.

Access your Application

The URL access is the one you got in the previous step. For this tutorial the URL is:
After the authentication, you will be connected to mattermost landing page.  If this is your first time connect to the page, you will be presented with the following screen.
Click on the check box "Remember my preference" & then "View in Browser"

Mattermost Changes

Site URL

Mattermost requires you to set the "Site URL".  This value should be set to the URL used to access the application, in this case:


Since we are configuring Mattermost to be accessed from a URL that will likely not match the address used to actually access the service, CORS needs to be adjusted to allow cross-origin requests.  
To update the CORS configuration, please refer to the official docs.  We recommend listing each domain or configuring the with the "*".


Create Your Own Mattermost Preview Instance


A Linux/Windows Machine with docker & docker-compose installed.


Create a working directory for the Mattermost instance. We’ll call this directory WORK_DIR.

Change directory into WORK_DIR

Create a directory called ziti_router

Create a file called .env

The .env file also holds the registration key for the edge router. You need to create an customer hosted edge router on the CloudZiti console and enter the registration key (REG_KEY) into this file.

Please follow this guide for the detail information on how to deploy edge router. In this example, our customer hosted edge router is named "Mattermost-ER"


Create a docker compose file (docker-compose.yaml) in your WORK_DIR, where you can define the services needed for Mattermost. In the following docker compose example, we showed two containers:

  • mattermost
  • edge router (er)

version: '3'
container_name: mattermost
image: mattermost/mattermost-preview
- ""
container_name: netfoundry-er
image: netfoundry/autonomous-router:latest
restart: unless-stopped
env_file: .env
- ./ziti_router:/etc/netfoundry

After you have created the file, start your Mattermost instance with the command:

docker-compose up -d


Was this article helpful?
0 out of 0 found this helpful



Article is closed for comments.