Which authentication approach is described as using two LDAP advanced policies and one SAML advanced policy within an nFactor flow to differentiate internal and partner users?

• A. A: Deploy SAML on Citrix ADC in the service provider role
• B. B: Create two LDAP and two SAML authentication policies
• C. C: Configure nFactor authentication with two LDAP advanced policies and one SAML advanced policy
• D. D: Configure two dedicated AAA virtual servers for internal and partner users

Answer: (C)

nFactor authentication flow lets you chain multiple authentication policies and decide the path based on policy results, so you can tailor the login experience to different user types in one session. Using two LDAP advanced policies alongside one SAML advanced policy inside an nFactor flow is exactly how you differentiate internal versus partner users in a single authentication attempt.

The LDAP advanced policies can inspect user attributes or group memberships from your internal directory to identify whether the user is internal. Based on that decision, the flow can route to the next step. The SAML advanced policy provides federation for partner users, authenticating them through a SAML IdP. By combining these in one nFactor sequence, internal users can be validated through LDAP, while partners can be authenticated via SAML, without needing separate login paths or servers.

This approach is preferable when the goal is to differentiate user types within a unified login experience and leverage the appropriate authentication method for each type, rather than duplicating policies or provisioning separate AAA infrastructure. The other options describe either different architectural setups or more policies than needed, but they don’t capture the dynamic, policy-driven routing within a single nFactor flow that distinguishes internal and partner users.