Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Fortinet Exam NSE7_LED-7.0 Topic 2 Question 39 Discussion

Actual exam question for Fortinet's NSE7_LED-7.0 exam
Question #: 39
Topic #: 2
[All NSE7_LED-7.0 Questions]

Refer to the exhibit.

Wireless guest users are unable to authenticate because they are getting a certificate error while loading the captive portal login page. This URL string is the HTTPS POST URL guest wireless users see when attempting to access the network using the web browser

Which two settings are the likely causes of the issue? (Choose two.)

Show Suggested Answer Hide Answer
Suggested Answer: A, B

According to the exhibit, the wireless guest users are getting a certificate error while loading the captive portal login page. This means that the browser cannot verify the identity of the server that is hosting the login page. Therefore, option A is true because the external server FQDN is incorrect, which means that it does not match the common name or subject alternative name of the server certificate. Option B is also true because the wireless user's browser is missing a CA certificate, which means that it does not have the root or intermediate certificate that issued the server certificate. Option C is false because the FortiGate authentication interface address is using HTTPS, which is a secure protocol that encrypts the communication between the browser and the server. Option D is false because the user address is not in DDNS form, which is not related to the certificate error.


Contribute your Thoughts:

Erick
11 hours ago
The certificate and the URL are the likely culprits here. I'm guessing someone set up the captive portal in a hurry and forgot to configure the certificates correctly.
upvoted 0 times
...
Jillian
4 days ago
Yes, SSL inspection settings could be blocking the connection. We should check that as well.
upvoted 0 times
...
Yuette
7 days ago
Hah, these wireless guest users must be tech-savvy enough to get a certificate error. Most would just assume it's broken and give up.
upvoted 0 times
...
Ressie
10 days ago
It could also be the SSL inspection settings causing the error.
upvoted 0 times
...
Stephen
10 days ago
I agree, the certificate authority could be the problem. Maybe it's not trusted.
upvoted 0 times
...
Jani
12 days ago
I bet it's the certificate and the URL mismatch. The URL in the image doesn't match the one the guest users are seeing, so it's not validating properly.
upvoted 0 times
Tyra
3 days ago
Maybe the certificate is expired, causing the error.
upvoted 0 times
...
...
Ruby
13 days ago
I think the issue might be with the certificate authority.
upvoted 0 times
...
Naomi
21 days ago
The certificate error is likely due to the use of a self-signed certificate. The HTTPS POST URL suggests the captive portal is using HTTPS, but the client doesn't trust the certificate.
upvoted 0 times
Graciela
10 days ago
The self-signed certificate is not trusted by the client.
upvoted 0 times
...
...

Save Cancel