There is a task to implement monitoring + unloading on servers in the network: let's say we have cloud storage with a bunch of servers and all this should be loaded evenly. Monitoring is done on the basis of Nagios.

A problem occurred with the implementation of request authentication.

Authentication here refers to the identification of requests from client machines to our servers in order to verify the validity of these requests.

Imagine, the client connects first to the balancer, the balancer analyzes the current server load and redirects the request to one of them. In this case, the server is notified that it has a new subscriber. However, if the servers have white IPs, nothing prevents the client, bypassing the balancer, from connecting to one of them. To prevent this from happening, you need to check a certain client id on the server, setting whether the client connected itself (then it needs to be blocked), or the balancer redirected it (then you can grant access).

Actually the question is how to implement the identification of user requests and whether it can be done by means of plug-ins or should it be done somehow else?

  • Nagios is not like something to do here, the pacemaker usually does load balancing. And he has inside ssl. - gbg
  • Thanks for the answer, this task has disappeared. - Lane

0