Anonymousprnt::Y
Click on images to see them in full screen

3-legged Authentication

Note: please be aware that in order 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.


Click Application type: Other, and name it.



The client ID is created, and is always accesible later...

The new credentials are available below...






Please note that 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 the above is complete you are ready to Authorize the application and test your connection. Note: After testing the connection you must submit the form.

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 .

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 will allow you to "feed" the Auth. code and the Auth. path to the form. We recommend that at this point you submit the form. You can of course test the connection and, all being well, you will see the number of rooms the system found for you.