Add condition in `doConnect` for checking network timeout is set

[pako81]

Description

Add condition in doConnect for verifying network timeout is set.

Motivation and Context

Removing the Network Timeout value in the Advanced tab of the LDAP wizard is breaking the LDAP configuration with no hints whatsoever of what is wrong. There is no check in place in the WebUI to force the use of this option so we should add a condition to check if this is set when calling doConnect.

How Has This Been Tested?

Manually by removing the Network Timeout value in the Advanced tab of the LDAP wizard and checking the LDAP configuration is still healthy.

Types of changes

• [X] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Database schema changes (next release will require increase of minor version instead of patch)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)
• [ ] Technical debt
• [ ] Tests only (no source changes)

Checklist:

• [X] Code changes
• [ ] Unit tests added
• [ ] Acceptance tests added
• [ ] Documentation ticket raised
• [ ] Changelog item

[CLAassistant]

All committers have signed the CLA.

[sonarcloud[bot]]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

100.0% Coverage
0.0% Duplication