304 · Question #106
When configuring authentication in VPE, which methods can be used for user authentication? (Select all that apply)
The correct answer is A. LDAP B. RADIUS C. SAML D. NTLM. VPE supports LDAP, RADIUS, SAML, and NTLM because these are all established user authentication protocols: LDAP queries directory services (like Active Directory), RADIUS provides centralized AAA for network access, SAML enables federated SSO via XML assertions, and NTLM is…
Question
When configuring authentication in VPE, which methods can be used for user authentication? (Select all that apply)
Options
- ALDAP
- BRADIUS
- CSAML
- DNTLM
- ETACACS+
- FOAuth
How the community answered
(32 responses)- A88% (28)
- E6% (2)
- F6% (2)
Explanation
VPE supports LDAP, RADIUS, SAML, and NTLM because these are all established user authentication protocols: LDAP queries directory services (like Active Directory), RADIUS provides centralized AAA for network access, SAML enables federated SSO via XML assertions, and NTLM is Microsoft's challenge-response protocol for Windows environments - all of which authenticate who a user is.
TACACS+ (E) is incorrect because it is primarily designed for authenticating administrators to network devices (routers, switches), not end users to applications or platforms - it's a device management AAA protocol, not a user identity protocol in this context.
OAuth (F) is incorrect because OAuth is an authorization framework, not an authentication protocol - it delegates access permissions, not identity verification. (OpenID Connect, which sits on top of OAuth, handles authentication, but OAuth alone does not.)
Memory tip: Think of the four correct answers as "LRSN - Legit Real Sign-in Networks" (LDAP, RADIUS, SAML, NTLM). The two wrong answers fail a simple test: TACACS+ is for devices, and OAuth is for access delegation - neither authenticates a user's identity directly.
Topics
Community Discussion
No community discussion yet for this question.