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?

Question

Options

• Ausername
• Bredir
• Cmagic
• Demail

• B
  4% (1)
• C
  88% (21)
• D
  8% (2)

Explanation

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". Exam Questions, Study Guides, Practice Tests. Lead the way to help you pass any IT Certification exams, 100% Pass Guaranteed or Full Refund. Especially Cisco, Microsoft, CompTIA, Citrix, EMC, HP, Oracle, VMware, Juniper, Check Point, LPI, Nortel, EXIN and so on. Our Slogan: First Test, First Pass. Help you to pass any IT Certification exams at the first try. You can reach us at any of the email addresses listed below. Any problems about IT certification or our products, you could rely upon us, we will give you satisfactory answers in 24 hours.

No community discussion yet for this question.