A direct link to the GitHub account

GitHub has updated its SCIM user responses to include profileUrl, a standard attribute defined by the System for Cross-domain Identity Management specification in RFC 7643. When an external identity is linked to a GitHub user, the attribute contains the absolute URL of that GitHub account.

The change addresses a gap in the information previously available through GitHub's SCIM responses. According to GitHub, matching a SCIM record with the corresponding GitHub account could previously require additional lookups or inference. Identity providers and IT teams can now read the account URL directly when processing the response.

Available through the Users endpoint

GitHub says profileUrl is returned from the SCIM /Users endpoint. The attribute is consistently supported across both organization and enterprise SCIM responses, allowing teams to use the same field when managing access at either level.

This consistency can simplify workflows that provision or manage GitHub access through an identity provider. A system receiving a SCIM user record can inspect profileUrl to establish the relationship between the external identity and the associated GitHub account, rather than relying on a separate matching process.

The field depends on identity linking

profileUrl is not present in every SCIM response. GitHub states that the attribute is omitted when an external identity has not yet been linked to a GitHub user. Systems consuming the response therefore need to treat the field as conditional and continue handling records where no linked account URL is available.

The omission distinguishes an unlinked external identity from a record that already corresponds to a GitHub account. The supplied changelog does not describe any change to how identities are linked, but it makes the result of that relationship easier to read when the link exists.

Existing attributes remain unchanged

GitHub says userName and other attributes continue to return the same values as before. The company characterizes the profileUrl addition as an additive change, meaning existing SCIM integrations can continue using their current fields without modification.

The changelog also says existing SCIM, GraphQL and identity management integrations are not affected. Organizations that do not need the new mapping can leave their current provisioning logic unchanged, while teams that want to use it can begin reading profileUrl whenever it is present in a response.

Documentation and next steps for adopters

The new attribute has been added to GitHub's SCIM OpenAPI schema and example responses. This gives developers and administrators a documented representation of the field when reviewing or updating integrations for enterprise or organization provisioning.

For teams that want to adopt the mapping, GitHub recommends starting to read profileUrl in SCIM responses when it is available. No action is required for existing integrations, according to the company's announcement. The supplied update does not identify any additional configuration, migration, or rollout requirement.

The change is focused on making an existing identity relationship more directly discoverable in SCIM data. By exposing the linked GitHub account URL in the response, GitHub gives identity providers and IT administrators another standardized attribute for account reconciliation and access-management workflows.

Sources

• GitHub ChangelogSCIM user responses now include a profileUrl attribute