nerdexam
CompTIA

CAS-001 · Question #431

Two separate companies are in the process of integrating their authentication infrastructure into a unified single sign-on system. Currently, both companies use an AD backend and two factor…

The correct answer is D. They should use the username format: [email protected], together with a password. Before full SSO integration is complete, users need a cross-domain authentication format that works with the established AD trust relationship. The User Principal Name (UPN) format - [email protected] - is the standard identifier used in Active Directory federation and…

Technical Integration of Enterprise Components

Question

Two separate companies are in the process of integrating their authentication infrastructure into a unified single sign-on system. Currently, both companies use an AD backend and two factor authentication using TOTP. The system administrators have configured a trust relationship between the authentication backend to ensure proper process flow. How should the employees request access to shared resources before the authentication integration is complete?

Options

  • AThey should logon to the system using the username concatenated with the 6-digit code and
  • BThey should logon to the system using the newly assigned global username:
  • CThey should use the username format: LAN\first.lastname together with their original password
  • DThey should use the username format: [email protected], together with a password

How the community answered

(61 responses)
  • A
    8% (5)
  • B
    15% (9)
  • C
    3% (2)
  • D
    74% (45)

Explanation

Before full SSO integration is complete, users need a cross-domain authentication format that works with the established AD trust relationship. The User Principal Name (UPN) format - [email protected] - is the standard identifier used in Active Directory federation and cross-domain trust scenarios. It uniquely identifies a user across organizational boundaries without ambiguity. Combined with their original password (and TOTP), this format allows the AD trust relationship to correctly route and validate credentials between the two backends. The other formats (LAN\ prefix, concatenated TOTP codes, or a new global username that hasn't been provisioned yet) are either non-standard, incomplete, or not yet available during the transition period.

Topics

#SSO federation#Active Directory trust#TOTP#identity integration

Community Discussion

No community discussion yet for this question.

Full CAS-001 Practice