Which SSO type requires the configuration of attribute mapping to exchange user information between the IdP and SP?

Question

Options

• ARADIUS SSO
• BRSA SecurID SSO
• CSAML SSO
• DKerberos SSO

• A
  4% (2)
• B
  2% (1)
• C
  92% (47)
• D
  2% (1)

Explanation

SAML (Security Assertion Markup Language) SSO is specifically designed around XML-based assertions that carry user attributes from the Identity Provider (IdP) to the Service Provider (SP), which is why attribute mapping configuration is a fundamental requirement - you must define how attributes like username, email, and roles get translated between systems. RADIUS is a network access protocol primarily used for authenticating remote/VPN users and passes credentials, not rich attribute maps between IdP and SP. RSA SecurID is a token-based MFA/authentication mechanism, not a federated SSO protocol that exchanges user attributes via a standardized mapping. Kerberos uses tickets for authentication within a trusted domain (typically Active Directory environments) and doesn't rely on configurable attribute mapping between an IdP and SP.

Memory tip: Think SAML = "Send Attributes, Map Labels" - the whole protocol revolves around asserting (sending) user attributes with a defined mapping schema, making it the go-to for web-based federated SSO across organizational boundaries.

No community discussion yet for this question.