A web application is unable to authenticate customers so they can access their bills.
The server administrator has tested the LDAP query but is not receiving results.
Which of the following is the NEXT step the server administrator should take to correct the problem?
A.
Check port 636 to see if it is being blocked. B.
Change service port 636 to port 389. C.
Restart the web server. D.
Verify the browser is using port 443.
A.
A web application is unable to authenticate customers so they can access their bills.
The server administrator has tested the LDAP query but is not receiving results.
Which of the following is the NEXT step the server administrator should take to correct the problem?
A.
Check port 636 to see if it is being blocked.
B.
Change service port 636 to port 389.
C.
Restart the web server.
D.
Verify the browser is using port 443.
A.
The correct answer is A. Check port 636 to see if it is being blocked.
Explanation:
LDAP (Lightweight Directory Access Protocol) is a protocol used for accessing and maintaining distributed directory information services over an Internet Protocol (IP) network. It is commonly used for authentication and authorization in web applications.
Port 636 is the default port used for secure LDAP (LDAPS), which uses SSL/TLS encryption to protect communication between the client and server. LDAPS is commonly used when sensitive information is being transmitted, such as login credentials.
If the server administrator is not receiving results when testing the LDAP query, it is possible that port 636 is being blocked. This could be due to a firewall or other security measure that is preventing traffic from reaching the server.
Therefore, the next step the server administrator should take is to check whether port 636 is being blocked. This can be done by using a network analyzer tool to capture traffic on the network and determine whether packets are being blocked or dropped.
If port 636 is indeed being blocked, the server administrator will need to work with the network administrator to allow traffic through the firewall or other security measure. Alternatively, they may need to switch to a different port, such as port 389, which is the default port used for LDAP without SSL/TLS encryption.
Changing the service port to port 389 (Option B) may resolve the issue if the problem is related to SSL/TLS encryption. However, this should only be done after confirming that port 636 is being blocked and that changing the port is a suitable solution.
Restarting the web server (Option C) is unlikely to resolve the issue if the problem is related to LDAP authentication. Similarly, verifying the browser is using port 443 (Option D) is not relevant to the issue at hand, as port 443 is used for HTTPS communication, not LDAP.