Fortinet FCSS_LED_AR-7.6 Exam - Topic 1 Question 3 Discussion

Actual exam question for Fortinet's FCSS_LED_AR-7.6 exam

Question #: 3
Topic #: 1

When troubleshooting a captive portal issue, which POST parameter in the redirected HTTPS request can be used to track the user's session and ensure that the request is valid?

Ausername

Bredir

Cmagic

Demail

Show Suggested Answer

Suggested Answer: C

In FortiGate captive portal workflows (local or external):

Client connects to SSID / interface that has captive portal enabled.

Client makes an HTTP/HTTPS request.

FortiGate intercepts and redirects to alogin page(local or external URL).

The portal form is submitted viaPOSTback to FortiGate.

To prevent tampering and to tie the POST back to thecorrect user session, FortiGate includes a special hidden parameter in the redirect and expects it in the POST:

The parameter is namedmagic.

The magic value:

Is aunique tokengenerated per captive-portal session.

Encodes/session-links the user's IP, interface, and session info.

Allows FortiGate to ensure that:

The POST comes from the user who initiated the original request.

The request is not a random or replayed submission.

When troubleshooting:

If the external portal does notpreserve and resendthe magic parameter back to FortiGate exactly as received, authentication fails, and you'll see errors like ''session not found'' or ''invalid magic''.

Why the other fields are not used for this purpose

A . username-- Just the login ID; multiple users can use the same username from different locations, so it can't uniquely track the browser session.

B . redir-- Contains the URL the user originally requested, so they can be sent back there after login. It is not a session integrity token.

D . email-- Optional field used in some guest/registration flows; irrelevant to session validation.

by Azalee at Dec 19, 2025, 10:57 PM

Limited Time Offer

25%

Off

Get Premium FCSS_LED_AR-7.6 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Georgiana

1 day ago

I agree, "magic" is the one used for session tracking.

upvoted 0 times

...

Goldie

6 days ago

"username" is not the right choice here.

upvoted 0 times

...

Iluminada

12 days ago

Wait, is "magic" really a thing? Sounds weird!

upvoted 0 times

...

Stephaine

17 days ago

I thought it was "redir" for sure.

upvoted 0 times

...

Emily

22 days ago

It's definitely the "magic" parameter!

upvoted 0 times

...

Tracey

27 days ago

Haha, "magic" parameter? What is this, Harry Potter? I'm going with B.

upvoted 0 times

...

Nguyet

2 months ago

C is the answer, obviously. The magic parameter is the key to unlocking the captive portal mystery.

upvoted 0 times

...

Jose

2 months ago

I'd go with option B. Seems like the most logical choice for a captive portal issue.

upvoted 0 times

...

Annamae

2 months ago

The redir parameter is the way to go here. Gotta track that session!

upvoted 0 times

...

Leonor

2 months ago

I thought "username" was important for identification, but I don't think it tracks the session itself.

upvoted 0 times

...

Sylvia

2 months ago

I feel like "redir" might be the one that helps with the redirect process, but I could be mixing it up with another question we did.

upvoted 0 times

...

Maybelle

3 months ago

I remember practicing a similar question where we discussed session management, but I can't recall if it was "magic" or "redir" that was the right answer.

upvoted 0 times

...

Tiara

3 months ago

I think the parameter we need is related to session tracking, but I'm not entirely sure which one it is.

upvoted 0 times

...

Raelene

3 months ago

Okay, I've got a strategy for this. I'll eliminate the obvious choices like username and email, and then focus on parameters that are more specific to the captive portal flow, like 'redir' or 'magic'. I think I've got a good shot at this.

upvoted 0 times

...

Irma

3 months ago

Ah, I think I've seen this before. If I remember correctly, the 'redir' parameter is often used to store the original URL the user was trying to access. That could be a good clue for tracking the session.

upvoted 0 times

...

Jesusa

3 months ago

I'm a bit confused on this one. I know captive portals use redirects, but I'm not sure which parameter would be used to track the session. I'll have to review my notes on captive portal troubleshooting.

upvoted 0 times

...

Deeanna

3 months ago

Okay, let's see. The key here is tracking the user's session, so I'm guessing it's probably not something like username or email. Maybe it's something more specific to the captive portal flow.

upvoted 0 times

...