I'm currently coding a integration WAPT
The goal is to allow the sysadmin to focus on managing their infrastructure and network, rather than worrying about server/network setup. This is the philosophy behind NethServer: a server with a Cockpit-based server manager.
To introduce myself, I'm a developer on the project, Stéphane de Labrusse, aka stephdl.
I've managed to achieve what I wanted, but I'm starting this thread to address what's not working as intended.
After installing the nethserver-wapt package, you should have
: - The waptserver wapttasks service started, ready to work with open wapt-1.3 authentication.
- If Samba AD authentication has been enabled (remotely or locally) on NethServer, wapt is ready for Kerberos authentication.
I have two questions
: 1- To start the service, I use a script that configures WAPT to use open authentication. I would like to be able to choose the authentication method and password; I don't know if this is possible (unless I submit a pull request?).
2- Is there a plan to run the WAPT server in gateway mode (with multiple network cards)? I haven't tried it for long, but I got WebSocket errors when the console tried to upload the wpt-agent. Is this theoretically possible?
