In a WLAN network using the Agile Controller as the admission controller, which of the following options are the reasons for Portal authentication failure? (Multiple choice)

Question

Options

• AThe key of the Agile Controller access device is inconsistent with the key configured on the device
• BThe billing cycle is not configured
• CPort 1814 is occupied on the server
• DAuthorization rule matching is to deny access

• A
  79% (31)
• B
  13% (5)
• C
  8% (3)

Explanation

Options A and D are correct because Portal authentication depends on two critical checkpoints: a valid trust relationship between the access device and the Agile Controller, and an authorization decision that permits access. When the shared key (used to authenticate RADIUS messages between the NAS device and the controller) does not match, the controller rejects the authentication exchange outright, causing Portal failure. Similarly, if an authorization rule explicitly denies the user, the controller blocks access regardless of whether credentials were valid.

Option B is wrong because the billing cycle relates to accounting and charging functions, not the authentication process itself - a missing billing cycle may affect how usage is tracked but does not block Portal authentication from completing. Option C is wrong because port 1814 is associated with RADIUS Change of Authorization (CoA), which is used to dynamically modify an already-established session; the core Portal authentication flow uses port 1812 (RADIUS authentication), so port 1814 being occupied does not cause authentication failure.

Memory tip: Focus on what happens before a user is admitted - key mismatch breaks the trust handshake (A), and a deny rule blocks the admission decision (D). Billing and CoA ports are post-authentication concerns and cannot cause Portal auth to fail.

No community discussion yet for this question.