Page 1 of 1

Web interface access

Published: Dec 16, 2019 - 09:56
by Hugo
Hello,

I haven't seen a topic on this subject, but I'd like to block access to the WAPT web interface.
Specifically, I want to block https://srvwapt.mydomain.lan.
Is it possible to do this, and even better, if it's possible to block certain groups of people while allowing access only to the network administrators?
WAPT community 1.7
Server: Debian 9
Client machines: Windows 10 and Windows 7
Regards

Re: Web interface access

Published: Dec 16, 2019 - 3:13 PM
by vcardon
Hugo wrote: Dec 16, 2019 - 9:56 AM I haven't seen a topic on this subject, but I'd like to block access to the WAPT web interface.
So, block https://srvwapt.mydomain.lan.
Is it possible to do this, and even better, if we can block certain groups of people while leaving access for the park administrators?
I think you can do this by configuring the Nginx of your WAPT server or the proxy in your organization.

The official Nginx documentation should be able to help you configure authenticated access using kerberos or htaccess.

For filtering via authenticating proxy, it will depend on what you use at home.

Sincerely.

Vincent

Re: Web interface access

Published: Dec 16, 2019 - 3:45 PM
by Hugo
Thank you for your quick reply, I will check the Nginx documentation.

Regards,
Hugo

Re: Web interface access

Published: Dec 16, 2019 - 4:27 PM
by Hugo
vcardon wrote: Dec 16, 2019 - 3:13 PM
I think you can do this by configuring the Nginx server on your WAPT server or the proxy within your organization.

The official Nginx documentation should help you configure authenticated access using Kerberos or .htaccess.

For filtering via an authenticating proxy, it will depend on what you use locally.

Regards,

Vincent
Can you tell me where the web files are located on the WAPT server?.

Re: Web interface access

Published: Dec 18, 2019 - 9:13 PM
by dcardon
Hello Hugo,
Hugo wrote: Dec 16, 2019 - 4:27 PM
vcardon wrote: Dec 16, 2019 - 3:13 PM
I think you can do this by configuring the Nginx server on your WAPT server or the proxy within your organization.

The official Nginx documentation should help you configure authenticated access using Kerberos or .htaccess.

For filtering via an authenticating proxy, it will depend on what you use locally.

Regards,

Vincent
Can you tell me where the web files are located on the WAPT server?.
This is a standard Nginx configuration with the configuration file located in /etc/nginx/sites-enabled/wapt.conf under Debian. You can then refer to the Nginx documentation. Be careful during your next upgrade. Running postconf.py overwrites the nginx wapt.conf file, and you will need to add your configuration again.

Sincerely,

Denis