What SAML attribute is required in the SAML assertion when configuring SAML SSO for a GitHub organization?
Select an answer to reveal the explanation.
Short Explanation and Infographic
When GitHub parses a SAML assertion, the one non-negotiable is the NameID — it's GitHub's way of uniquely identifying the user. Without it, GitHub can't match the SAML identity to a GitHub account.
Full explanation below image
Full Explanation
When configuring SAML SSO for GitHub organizations or enterprises, the NameID element in the SAML assertion is required. GitHub uses the NameID as the persistent unique identifier to link a user's IdP identity to their GitHub account. The NameID format should ideally be a persistent, non-transient value like an email address or employee ID. While 'email' is a commonly mapped attribute and GitHub recommends mapping it, it is not the required assertion element — NameID is. 'displayName' and 'memberOf' are optional attributes that can enhance user experience but are not required for SAML SSO to function.