N-able N-central HTTPS service indicates Normal when the login and password is incorrect

Last Modified

Mon Aug 13 18:25 GMT 2018

Description

When N-able N-central , agent or probe is monitoring a website via HTTPS, a username, password and authentication scheme. When inputting a username and password for a web form login, the service status is normal, even with an incorrect username and password:
HTTPS Status Code200
Successful LoginTrue

Environment

  • N-able N-central 10 or later

Solution

This is expected behaviour.

The username and password field are used for access to the page itself via HTTPS protocol. So, if a response is provided (status code: 200), the service will return with a Normal status. The username and password is not used to login to a webform within the page, it is the access to the page itself.

The purpose of the username and password field is for webpage access (e.g. a user mentioned in a .htaccess file) and not web application login.

The following authentication schemes can be used.
Authentication Scheme

The security authentication scheme used by the designated URL for determining if requests are valid or not. Configure this property using one of:

  • Basic
  • Digest
  • NTLM
  • Kerberos
  • Negotiate