Which type of SSO should you choose if you want to enable transparent authentication for domain-joined Windows devices without requiring users to enter credentials?

Question

Options

• ASAML SSO
• BKerberos SSO
• CRADIUS SSO
• DRSA SecurID SSO

• A
  4% (1)
• B
  88% (23)
• C
  4% (1)
• D
  4% (1)

Explanation

Kerberos SSO is the right choice because it's natively integrated into Active Directory and Windows domain environments - when a user logs into a domain-joined machine, Windows automatically obtains a Kerberos ticket-granting ticket (TGT), which can be silently presented to authenticate against other services without any additional credential prompts. This is the foundation of Windows Integrated Authentication (NTLM/Kerberos).

Why the others are wrong:

• A (SAML SSO) is a federation protocol for web-based apps (e.g., cloud services); it requires a browser redirect flow and doesn't natively leverage Windows domain credentials transparently.
• C (RADIUS SSO) is used for network access authentication (VPNs, Wi-Fi) - not for transparent desktop/application SSO on domain-joined machines.
• D (RSA SecurID SSO) is a multi-factor/token-based authentication product, not a transparent SSO mechanism for domain environments.

Memory tip: Think "Kerberos = Kingdom" - it's the gatekeeper of the Windows domain kingdom. Once you're inside the kingdom (domain-joined), you get a magic ticket (TGT) that opens all the doors silently. Any question mentioning "domain-joined," "Windows," or "transparent/no credentials" should immediately point you to Kerberos.

No community discussion yet for this question.