GH-100 · Domain 1: Manage GitHub identities and access · 19% of the exam
Task 1.1: Manage user identities and authentication
Enterprise Managed Users against personal accounts, SAML single sign-on and two-factor requirements, SCIM provisioning and team synchronization, choosing an identity provider, and how GitHub authenticates people and authorizes their credentials.
Study it
Enterprise Managed Users and personal accounts, SAML single sign-on and two-factor requirements
Lesson coming
SCIM provisioning, team synchronization and identity providers
Lesson coming
How GitHub authenticates people and authorizes their credentials
Lesson coming
Sample questions
Try each one before opening the answer. Every option is explained, with the GitHub documentation page that proves it.
Question 1 · choose 1
An enterprise on GitHub Enterprise Cloud uses personal accounts in 12 organizations. Each organization has its own SAML single sign-on and SCIM integration, so that leavers are removed automatically. A new rule requires every member to authenticate through the identity provider before reaching any internal repository, and SCIM deprovisioning must stay. The developers work only on company repositories. What should the company do?
AConfigure SAML on the enterprise account, and keep the SCIM integration in each organization
BConfigure SAML on the enterprise account, and move the SCIM integration to the enterprise account
CKeep the organization-level setup, and move every internal repository into a single organization that enforces SAML
DCreate an enterprise with managed users, whose identity provider handles both authentication and SCIM provisioning
Show the answer and why
AConfigure SAML on the enterprise account, and keep the SCIM integration in each organization
Incorrect
Without managed users, SCIM needs SAML configured at the organization level, which the enterprise configuration overrides.
BConfigure SAML on the enterprise account, and move the SCIM integration to the enterprise account
Incorrect
SCIM isn't available for an enterprise account without Enterprise Managed Users.
CKeep the organization-level setup, and move every internal repository into a single organization that enforces SAML
Incorrect
Organization-level SAML doesn't make members of the enterprise authenticate before reaching internal repositories.
DCreate an enterprise with managed users, whose identity provider handles both authentication and SCIM provisioning
Correct
Managed users must authenticate on the identity provider to reach any of the enterprise's resources, and the provider provisions them with SCIM.
With personal accounts, SAML at the organization level doesn't require members to authenticate through SAML to reach internal repositories; SAML on the enterprise account does, and it overrides every organization's SAML configuration. But without Enterprise Managed Users, SCIM is available only with SAML configured at the organization level, never on the enterprise account. Keeping both needs an enterprise with managed users, which is created as a new enterprise account: the identity provider provisions the accounts with SCIM, and users must authenticate there to reach the enterprise's resources.
An enterprise with managed users is moving its authentication and provisioning from Okta to Entra ID, and the normalized SCIM userName values stay the same. Two integrations run against its organizations: a nightly script that uses a personal access token (classic) of the managed user svc-reports, and a deployment tool that runs as a GitHub App installed on the organizations. Which integrations will need new credentials after the move?
AOnly the script, because its token is deleted during the move while the app installation stays in place
BNeither, because an owner edits the existing SAML configuration to point at Entra ID
CBoth, because the move removes the app's installation along with the users' tokens
DNeither, because the token is linked again when svc-reports is reprovisioned with the same normalized userName
Show the answer and why
AOnly the script, because its token is deleted during the move while the app installation stays in place
Correct
The move disables authentication, which deletes classic tokens of managed users and leaves GitHub App installations in place.
BNeither, because an owner edits the existing SAML configuration to point at Entra ID
Incorrect
The existing configuration can't be edited; the move disables authentication and then reconfigures it.
CBoth, because the move removes the app's installation along with the users' tokens
Incorrect
GitHub App installations remain in place when authentication is disabled, so the tool keeps working.
DNeither, because the token is linked again when svc-reports is reprovisioned with the same normalized userName
Incorrect
Reprovisioning links the account, but its classic token was deleted when authentication was disabled.
An enterprise with managed users can't edit its existing authentication and provisioning configuration: to move to a new identity provider it disables authentication, then reconfigures authentication and SCIM, and users are reprovisioned and linked by their normalized userName. Disabling authentication deletes personal access tokens (classic), SSH keys and OAuth app authorizations of managed user accounts, while GitHub App installations and other organization-owned resources stay in place. The script needs a new token; the app keeps working.
An enterprise with managed users uses Entra ID for single sign-on and SCIM provisioning. A contractor leaves for a six-week break and will come back. During the break she must have no access. On her return the enterprise wants her existing account back, with her username and her forks of internal repositories restored. What should the identity team do in Entra ID when the break starts?
ASoft-delete her user in Entra ID, then restore it from Deleted users when she returns
BDisable her user in Entra ID, then enable it again when she returns
CHave a script send a SCIM DELETE request for her user, then provision her again when she returns
DUnassign her from the application, then assign a new Entra ID user with the same email address when she returns
Show the answer and why
ASoft-delete her user in Entra ID, then restore it from Deleted users when she returns
Incorrect
Entra ID hard-deletes soft-deleted users after 30 days, which hard-deprovisions the account before she returns.
BDisable her user in Entra ID, then enable it again when she returns
Correct
Disabling sends a soft-deprovision: the account is suspended and can be reinstated, and forks come back within 90 days.
CHave a script send a SCIM DELETE request for her user, then provision her again when she returns
Incorrect
A DELETE request hard-deprovisions the account, which can't be unsuspended.
DUnassign her from the application, then assign a new Entra ID user with the same email address when she returns
Incorrect
Reinstatement needs the same IdP user account, because the suspended account stays linked to that external identity.
Deprovisioning always suspends a managed user account and never deletes it. A soft-deprovision, such as disabling the user in Entra ID, can be reversed by reprovisioning the same IdP user: the username comes back, and deleted forks of private or internal repositories are restored if the account is unsuspended within 90 days. A hard-deprovision, such as a SCIM DELETE or the hard-deletion that Entra ID performs 30 days after a soft-delete, can't be reversed.
An organization requires SSH certificates from its own certificate authority for Git access, and an internal system issues each developer a certificate that is valid for seven days. A developer's laptop, holding a certificate issued yesterday, is stolen. Security wants that certificate rejected at once; the other developers can get new certificates from the issuing system within the hour. What should the owner do?
ARemove the CA that signed it from the organization, then add a new CA and issue certificates from it
BRevoke that one certificate in the organization's SSH certificate authority settings, keeping the CA in place
CDelete the SSH public keys stored on the developer's account
DAdd a source-address extension to the CA so the certificate only works from the office network
Show the answer and why
ARemove the CA that signed it from the organization, then add a new CA and issue certificates from it
Correct
Removing a CA immediately stops GitHub accepting every certificate it signed, including unexpired ones.
BRevoke that one certificate in the organization's SSH certificate authority settings, keeping the CA in place
Incorrect
An issued certificate can't be revoked on its own while the same CA is still trusted.
CDelete the SSH public keys stored on the developer's account
Incorrect
GitHub validates the certificate by its signature, fields and trusted CA, not by keys stored on the account.
DAdd a source-address extension to the CA so the certificate only works from the office network
Incorrect
Extensions are part of each certificate when it's signed; the stolen certificate keeps the fields it was issued with.
OpenSSH certificates have no revocation lists, so GitHub can't revoke one issued certificate while it still trusts the signing CA. To invalidate certificates before they expire, remove the CA from the organization or enterprise settings; this invalidates every certificate it signed, so new certificates must come from a new CA.
A company is setting up a new enterprise with managed users. Its business units use Entra ID and Okta. Which two statements about its identity provider choice are true? (Choose TWO.)
AGitHub applies the IdP's Conditional Access Policy only with OIDC and Entra ID
BPingFederate can provide OIDC sign-in with Conditional Access Policy support
COkta for sign-in with Entra ID for provisioning isn't supported
DA system that isn't a partner IdP may authenticate users with OIDC if it provisions them with SCIM 2.0
EAfter SAML is set up, an enterprise owner can edit the sign-on URL and issuer in place
Show the answer and why
AGitHub applies the IdP's Conditional Access Policy only with OIDC and Entra ID
Correct
OIDC and Conditional Access Policy support for Enterprise Managed Users is available only for Entra ID.
BPingFederate can provide OIDC sign-in with Conditional Access Policy support
Incorrect
OIDC with Conditional Access Policy support is available only with Entra ID.
COkta for sign-in with Entra ID for provisioning isn't supported
Correct
That combination is explicitly not supported, and GitHub's SCIM API returns an error to provisioning attempts.
DA system that isn't a partner IdP may authenticate users with OIDC if it provisions them with SCIM 2.0
Incorrect
Other identity management systems must provide authentication with SAML.
EAfter SAML is set up, an enterprise owner can edit the sign-on URL and issuer in place
Incorrect
Only the SAML certificate can be updated; new URLs require disabling and reconfiguring SAML SSO.
Partner identity providers give a paved-path integration for both authentication and provisioning, and GitHub doesn't support mixing Okta and Entra ID for SSO and SCIM. OIDC, with support for the IdP's Conditional Access Policy, is available only with Entra ID; other identity systems must authenticate with SAML and provision with SCIM. After SAML SSO is configured, only its certificate can be changed in place.
A company has just created an enterprise with managed users on GitHub.com, with the short code fabrikam. Before any user is provisioned, someone must sign in to configure authentication and provisioning. Which account is that?
AThe first user that the identity provider provisions through SCIM
Bfabrikam_admin, the setup user created with the enterprise
CThe personal account of the person who signed the contract
DAn account named admin@fabrikam that the identity provider creates
Show the answer and why
AThe first user that the identity provider provisions through SCIM
Incorrect
No managed user exists until provisioning is configured by the setup user.
Bfabrikam_admin, the setup user created with the enterprise
Correct
On GitHub.com the setup user's username is the enterprise's short code followed by _admin.
CThe personal account of the person who signed the contract
Incorrect
Managed user enterprises are configured by the setup user, not a personal account.
DAn account named admin@fabrikam that the identity provider creates
Incorrect
The setup user is created with the enterprise and named after its short code.
When an enterprise with managed users is created on GitHub.com, GitHub creates a setup user whose username is the enterprise's short code suffixed with _admin, such as fabrikam_admin. The setup user configures authentication and provisioning for the enterprise.
An enterprise with personal accounts uses team synchronization with Entra ID for its organization teams. A new hire is added to an Entra ID group that is linked to a team in the web organization, but she isn't a member of that organization yet. What happens?
AShe isn't added: team synchronization can't add people to organizations they don't already belong to
BShe becomes a member of the web organization and joins the team at the next sync
CShe becomes an outside collaborator on the team's repositories
DShe receives an enterprise team membership instead of the organization team
Show the answer and why
AShe isn't added: team synchronization can't add people to organizations they don't already belong to
Correct
Team sync manages team membership only for people who already have access to the organization.
BShe becomes a member of the web organization and joins the team at the next sync
Incorrect
Adding users to organizations through IdP groups is a capability of Enterprise Managed Users, not team sync.
CShe becomes an outside collaborator on the team's repositories
Incorrect
Team sync doesn't create collaborators; it can't add people who lack access.
DShe receives an enterprise team membership instead of the organization team
Incorrect
Team sync with personal accounts works only with organization teams.
With personal accounts, team synchronization lets an Entra ID or Okta group manage an organization team's membership and the privileges linked to it, but it can't add users to organizations where they don't already have access. With Enterprise Managed Users, IdP groups can also add users to organizations.
An organization adds a new SSH certificate authority today. Its internal issuing system signs developer certificates with ssh-keygen but doesn't pass the -V option. What does GitHub require of these certificates?
ANothing; a lifetime is optional for certificates from any CA
BA lifetime of less than 366 days, set with -V when each certificate is signed
CA lifetime of no more than 24 hours, set in the organization's settings
DA lifetime configured once on the CA in the organization settings, not on each certificate
Show the answer and why
ANothing; a lifetime is optional for certificates from any CA
Incorrect
Only CAs uploaded before March 27, 2024 may issue certificates without a lifetime.
BA lifetime of less than 366 days, set with -V when each certificate is signed
Correct
For CAs uploaded after March 27, 2024, certificates must be signed with a lifetime under 366 days.
CA lifetime of no more than 24 hours, set in the organization's settings
Incorrect
The lifetime is set with -V on each certificate and must be under 366 days.
DA lifetime configured once on the CA in the organization settings, not on each certificate
Incorrect
The lifetime is part of each certificate, set with -V when it is signed.
When you issue an SSH certificate, you include an extension that names the GitHub user it is for. For CAs uploaded after March 27, 2024, you must use the -V flag to give each certificate a lifetime of less than 366 days; CAs uploaded earlier may issue certificates without one unless they are upgraded to enforce the requirement.