Click on images to see them in full screen


From version 9.1 of Door Tablet we support 3-legged authentication. Previously, Door Tablet only supported 2-legged authentication. This method is sufficient for organisations with domain wide authorisation. For larger organisations, 3-legged authentication is required. This limits access to resources based on a specific admin user. Door Tablet will only be able to access resources that an administrator has been granted access to.

Note: to use Door Tablet with 3-legged authentication the Door Tablet server must be enabled for HTTPS. See here Database 'Door Tablet HELP', View 'Help Documents', Document 'Enabling HTTPS'.

When using 3-legged authentication, the process mandates the involvement of a "user", which owns the data Door Tablet will access.

When setting up Google Workspace for 3-legged authentication you will acquire three items, which are required in Door Tablet:

  1. Client ID
  2. Client Secret
  3. User email (account owner's email)
These will be marked for you, as we set Google Workspace.

Start by creating a project here:

Proceed to Credentials:

Click Application type: Other, and name it.

The client ID is created, and is now accessible.

The new credentials are available below

The links above will relate to your own Door Tablet server, which you will need to secure (SSL).

The OAuth consent screen requires that you name the application and add scopes.

Scopes that are required:

Note: to add the scopes below, all Authorised Redirect URIs must use HTTPS. Therefore, the Door Tablet Server must be enabled for HTTPS. See here Database 'Door Tablet HELP', View 'Help Documents', Document 'Enabling HTTPS'.

Once this is complete you are ready to authorize the application and test your connection.

Please copy the Client ID and Client secret from the project credentials. Door Tablet also shows the Authorised Redirect URI that you must register, as shown above. Click on 'Authorize Connection'.

You will now be prompted to Sign in

You are now ready to authorize the application:

Once you click on 'Allow', the following popup will show, which allows you to input the Auth. code and the Auth. path into the form. At this point we recommend that you submit the form. You can test the connection and, all being well, you will see the number of rooms the system found for you.

Note: in some configurations the ability to use the code automatically will not work. You will be prompted to collect the code manually.

The above action will result in both the Auth. code and the Auth. path being updated on the form.

You are now ready to click the 'Check Connection' button:

Note: After testing the connection you must submit the form.