Web Authorization

Supported browsers:
Google Chrome, version >= 76
Firefox, version >= 71
Safari, version >= 13

In this type of authorization any request from an unauthenticated user sent via a web browser will be redirected to a special authorization page of SafeUTM. After successful authorization, you will be redirected to the specified request.

For this type of authorization, the user must have the IP address of the SafeUTM LANlocal network interface mustspecified beon specifiedthe network card as thea defaultgateway gateway.(chained into a gateway chain) or for direct connections to a proxy. Also, DNS address resolution must work before connecting to the internet,Internet, DNS resolution of addresses must work, otherwise the browser request to the example.com browser requestaddress will not be redirected to the gateway and,and accordingly,the loginusername and password request will not appear in the browser.

You can check name resolution in Windows using the command: nslookup google.com. The output of this command must contain IP addresses.

To configure authorization via web interface, go to Users -> Authorization and select Web Authorization and Authorization via Web Interface, as shown in the screenshot below:

Next,After logfilling in underthe Domain name field and saving the accountsettings, ofa Let’s Encrypt certificate will be issued and the selected user will be redirected to the authorization window, bypassing the security exception page:

If a certificate for such a domain has already been loaded in the Certificates section, then it will be used and a new certificate will not be issued.

Next, try to access the internet via a web browser. An authorization window should appear where you need to type in the account’s login and password of the user created on SafeUTM. The authorization window can be seen in the screenshot below:

When the user is authenticated via web, access to the internet will be provided until the authorization is forcibly canceled or terminated due to user’s inactivity.

When logging into an HTTPS website, the user must confirm trust to the SafeUTM certificate. Alternatively, the certificate can be added to trusted root certification centers on the device (for example, through domain policies).

It is recommended to specify the IP address of the local SafeUTM as DNS server on the LAN computers and devices.

You can learn more about authorization of Active Directory (SSO-authentication)users by clicking on this link.link.