We've recently moved some of the REST API documentation. If you can't find what you're looking for, you might try the Actions REST API page.
SCIM
Benutzererstellung und Teammitgliedschaften können mithilfe der SCIM-API automatisiert werden.
Hinweis: SCIM für GitHub Enterprise Server befindet sich derzeit in der privaten Betaphase, Änderungen vorbehalten. Wenn du Zugang zur Betaversion erhalten möchtest, kontaktiere deinen Kundenbetreuer unter GitHub-Vertriebsteam. Hinterlasse Feedback in der GitHub-Community-Diskussion.
Warnung: Die Betaversion dient ausschließlich zu Testzwecken und zum Erhalt von Feedback, es wird kein Support bereitgestellt. GitHub empfiehlt das Testen mit einer Staginginstanz. Weitere Informationen findest du unter Einrichten einer Staginginstanz.
Informationen zur SCIM-API
GitHub Enterprise Server stellt eine SCIM-API für die Verwendung durch SCIM-fähige Identitätsanbieter (Identity Providers, IdP) bereit. Bei einer Integration mit dem IdP können mithilfe der API Benutzerkonten in einer GitHub Enterprise Server-Instanz, die das einmalige Anmelden mit SAML zur Authentifizierung verwendet, automatisch bereitgestellt, verwaltet oder die Bereitstellung aufgehoben werden. Weitere Informationen zum einmaligen Anmelden mit SAML findest du unter Informationen zu SAML for Enterprise IAM.
Die SCIM-API basiert auf SCIM 2.0. Weitere Informationen findest du in der Spezifikation.
Endpunkt-URLs für die SCIM-API
Ein Identitätsanbieter kann über die folgende Stamm-URL mit der SCIM-API für eine GitHub Enterprise Server-Instanz kommunizieren.
http(s)://HOSTNAME/api/v3/scim/v2/
Bei Endpunkt-URLs für die SCIM-API muss die Groß-/Kleinschreibung beachtet werden. Beispielsweise muss der erste Buchstabe des Users-Endpunkts großgeschrieben werden.
GET /scim/v2/Users/{scim_user_id}
Authentifizieren von Aufrufen der SCIM-API
Bei der SCIM-Integration mit dem Identitätsanbieter werden Aktionen im Auftrag eines Unternehmensbesitzers für die GitHub Enterprise Server-Instanz ausgeführt. Weitere Informationen findest du unter Rollen in einem Unternehmen.
Zur Authentifizierung von Anforderungen an die API ist für die SCIM-Konfiguration beim Identitätsanbieter personal access token mit dem Bereich admin:enterprise erforderlich, die der IdP im Authorization-Header der Anforderung bereitstellen muss. Weitere Informationen zu personal access tokens findest du unter Erstellen von personal access token.
Hinweis: Unternehmensbesitzer müssen für die Authentifizierung von Anforderungen an die SCIM-API personal access token generieren und verwenden. Aufrufer der GitHub-App werden derzeit nicht unterstützt.
Informationen zur Zuordnung von SAML- und SCIM-Daten
Die GitHub Enterprise Server-Instanz verknüpft alle Benutzerinnen, die sich erfolgreich über die einmalige Anmeldung mit SAML authentifiziert haben, mit einer SCIM-Identität. Für eine erfolgreiche Verknüpfung der Identitäten müssen der SAML-Identitätsanbieter und die SCIM-Integration für alle Benutzerinnen übereinstimmende SAML-NameID- und SCIM-userName-Werte verwenden.
Unterstützte SCIM-Benutzerattribute
Die User-Endpunkte der SCIM-API unterstützen innerhalb eines Anforderungsparameters die folgenden Attribute.
| Name | type | BESCHREIBUNG |
|---|---|---|
displayName | String | Für Menschen lesbarer Benutzername. |
name.formatted | String | Der vollständige und für die Anzeige formatierte Name des Benutzers/der Benutzerin, einschließlich aller zweiter Vornamen, Titel und Namenszusätze. |
name.givenName | String | Der Vorname des Benutzers. |
name.familyName | String | Der Nachname des Benutzers. |
userName | String | Der vom Identitätsanbieter generierte Benutzername des Benutzers/der Benutzerin. Wird vor der Verwendung einer Normalisierung unterzogen. |
emails | Array | Liste der Benutzer-E-Mails. |
roles | Array | Liste der Benutzerrollen. |
externalId | String | Dieser Bezeichner wird von einem Identitätsanbieter generiert. Du findest die externalId für Benutzer*innen entweder beim Identitätsanbieter oder indem du den Endpunkt zum Auflisten durch SCIM bereitgestellter Identitäten verwendest und nach anderen bekannten Attributen filterst, z. B. dem Benutzernamen oder der E-Mail-Adresse in der GitHub Enterprise Server-Instanz. |
id | String | Vom SCIM-Endpunkt der Instanz generierter Bezeichner. |
active | Boolean | Gibt an, ob die Identität aktiv ist (true) oder angehalten werden soll (false). |
List provisioned SCIM groups for an enterprise
Note: The SCIM API endpoints for enterprise accounts are currently in private beta and are subject to change.
Lists provisioned SCIM groups in an enterprise.
You can improve query search time by using the excludedAttributes query parameter with a value of members to exclude members from the response.
Parameter
| Headers |
|---|
| Name, Type, Description |
acceptstringSetting to |
| Query parameters |
| Name, Type, Description |
filterstringIf specified, only results that match the specified filter will be returned. Multiple filters are not supported. Possible filters are |
excludedAttributesstringExcludes the specified attribute from being returned in the results. Using this parameter can speed up response time. |
startIndexintegerUsed for pagination: the starting index of the first result to return when paginating through values. Default: |
countintegerUsed for pagination: the number of results to return per page. Default: |
HTTP-Antwortstatuscodes
| Statuscode | BESCHREIBUNG |
|---|---|
200 | Success, either groups were found or not found |
400 | Bad request |
401 | Authorization failure |
403 | Permission denied |
429 | Too many requests |
500 | Internal server error |
Codebeispiele
curl \
-H "Accept: application/scim+json" \
-H "Authorization: Bearer <YOUR-TOKEN>" \
http(s)://HOSTNAME/api/v3/scim/v2/GroupsSuccess, either groups were found or not found
Status: 200{
"schemas": [
"urn:ietf:params:scim:api:messages:2.0:ListResponse"
],
"totalResults": 1,
"Resources": [
{
"schemas": [
"urn:ietf:params:scim:schemas:core:2.0:Group"
],
"externalId": "8aa1a0c0-c4c3-4bc0-b4a5-2ef676900159",
"id": "927fa2c08dcb4a7fae9e",
"displayName": "Engineering",
"members": [
{
"value": "879db59-3bdf-4490-ad68-ab880a2694745",
"$+ref": "https://api.github.localhost/scim/v2/Users/879db59-3bdf-4490-ad68-ab880a2694745",
"displayName": "User 1"
},
{
"value": "0db508eb-91e2-46e4-809c-30dcbda0c685",
"$+ref": "https://api.github.localhost/scim/v2/Users/0db508eb-91e2-46e4-809c-30dcbda0c685",
"displayName": "User 2"
}
],
"meta": {
"resourceType": "Group",
"created": "2012-03-27T19:59:26.000Z",
"lastModified": "2018-03-27T19:59:26.000Z",
"location": "https://api.github.localhost/scim/v2/Groups/927fa2c08dcb4a7fae9e"
}
}
],
"startIndex": 1,
"itemsPerPage": 20
}Provision a SCIM enterprise group
Note: The SCIM API endpoints for enterprise accounts are currently in private beta and are subject to change.
Creates a SCIM group for an enterprise.
If members are included as part of the group provisioning payload, they will be created as external group members. It is up to a provider to store a mapping between the externalId and id of each user.
Parameter
| Headers | ||||||
|---|---|---|---|---|---|---|
| Name, Type, Description | ||||||
acceptstringSetting to | ||||||
| Body parameters | ||||||
| Name, Type, Description | ||||||
schemasarray of stringsRequiredThe URIs that are used to indicate the namespaces of the SCIM schemas. | ||||||
externalIdstringRequiredA unique identifier for the resource as defined by the provisioning client. | ||||||
displayNamestringRequiredA human-readable name for a security group. | ||||||
membersarray of objectsRequiredThe group members. | ||||||
Properties of | ||||||
| Name, Type, Description |
|---|
valuestringRequiredThe local unique identifier for the member |
displayNamestringRequiredThe display name associated with the member |
HTTP-Antwortstatuscodes
| Statuscode | BESCHREIBUNG |
|---|---|
201 | Group has been created |
400 | Bad request |
401 | Authorization failure |
403 | Permission denied |
409 | Duplicate record detected |
429 | Too many requests |
500 | Internal server error |
Codebeispiele
curl \
-X POST \
-H "Accept: application/scim+json" \
-H "Authorization: Bearer <YOUR-TOKEN>" \
http(s)://HOSTNAME/api/v3/scim/v2/Groups \
-d '{"schemas":["urn:ietf:params:scim:schemas:core:2.0:Group"],"externalId":"8aa1a0c0-c4c3-4bc0-b4a5-2ef676900159","displayName":"Engineering"}'Group has been created
Status: 201{
"schemas": [
"urn:ietf:params:scim:schemas:core:2.0:Group"
],
"id": "abcd27f8-a9aa-11ea-8221-f59b2be9cccc",
"externalId": "8aa1a0c0-c4c3-4bc0-b4a5-2ef676900159",
"displayName": "Engineering",
"members": [
{
"value": "879db59-3bdf-4490-ad68-ab880a2694745",
"$+ref": "https://api.github.localhost/scim/v2/Users/879db59-3bdf-4490-ad68-ab880a2694745",
"displayName": "User 1"
},
{
"value": "0db508eb-91e2-46e4-809c-30dcbda0c685",
"$+ref": "https://api.github.localhost/scim/v2/Users/0db508eb-91e2-46e4-809c-30dcbda0c685",
"displayName": "User 2"
}
],
"meta": {
"resourceType": "Group",
"created": "2012-03-27T19:59:26.000Z",
"lastModified": "2018-03-27T19:59:26.000Z",
"location": "https://api.github.localhost/scim/v2/Groups/927fa2c08dcb4a7fae9e"
}
}Get SCIM provisioning information for an enterprise group
Note: The SCIM API endpoints for enterprise accounts are currently in private beta and are subject to change.
Gets information about a SCIM group.
Parameter
| Headers |
|---|
| Name, Type, Description |
acceptstringSetting to |
| Path parameters |
| Name, Type, Description |
scim_group_idstringRequiredA unique identifier of the SCIM group. |
| Query parameters |
| Name, Type, Description |
excludedAttributesstringExcludes the specified attribute from being returned in the results. Using this parameter can speed up response time. |
HTTP-Antwortstatuscodes
| Statuscode | BESCHREIBUNG |
|---|---|
200 | Success, a group was found |
400 | Bad request |
401 | Authorization failure |
403 | Permission denied |
404 | Resource not found |
429 | Too many requests |
500 | Internal server error |
Codebeispiele
curl \
-H "Accept: application/scim+json" \
-H "Authorization: Bearer <YOUR-TOKEN>" \
http(s)://HOSTNAME/api/v3/scim/v2/Groups/SCIM_GROUP_IDSuccess, a group was found
Status: 200{
"schemas": [
"urn:ietf:params:scim:schemas:core:2.0:Group"
],
"id": "abcd27f8-a9aa-11ea-8221-f59b2be9cccc",
"externalId": "8aa1a0c0-c4c3-4bc0-b4a5-2ef676900159",
"displayName": "Engineering",
"members": [
{
"value": "879db59-3bdf-4490-ad68-ab880a2694745",
"$+ref": "https://api.github.localhost/scim/v2/Users/879db59-3bdf-4490-ad68-ab880a2694745",
"displayName": "User 1"
},
{
"value": "0db508eb-91e2-46e4-809c-30dcbda0c685",
"$+ref": "https://api.github.localhost/scim/v2/Users/0db508eb-91e2-46e4-809c-30dcbda0c685",
"displayName": "User 2"
}
],
"meta": {
"resourceType": "Group",
"created": "2012-03-27T19:59:26.000Z",
"lastModified": "2018-03-27T19:59:26.000Z",
"location": "https://api.github.localhost/scim/v2/Groups/927fa2c08dcb4a7fae9e"
}
}Set SCIM information for a provisioned enterprise group
Note: The SCIM API endpoints for enterprise accounts are currently in private beta and are subject to change.
Replaces an existing provisioned group’s information.
You must provide all the information required for the group as if you were provisioning it for the first time. Any existing group information that you don't provide will be removed, including group membership. If you want to only update a specific attribute, use the Update an attribute for a SCIM enterprise group endpoint instead.
Parameter
| Headers | ||||||
|---|---|---|---|---|---|---|
| Name, Type, Description | ||||||
acceptstringSetting to | ||||||
| Path parameters | ||||||
| Name, Type, Description | ||||||
scim_group_idstringRequiredA unique identifier of the SCIM group. | ||||||
| Body parameters | ||||||
| Name, Type, Description | ||||||
schemasarray of stringsRequiredThe URIs that are used to indicate the namespaces of the SCIM schemas. | ||||||
externalIdstringRequiredA unique identifier for the resource as defined by the provisioning client. | ||||||
displayNamestringRequiredA human-readable name for a security group. | ||||||
membersarray of objectsRequiredThe group members. | ||||||
Properties of | ||||||
| Name, Type, Description |
|---|
valuestringRequiredThe local unique identifier for the member |
displayNamestringRequiredThe display name associated with the member |
HTTP-Antwortstatuscodes
| Statuscode | BESCHREIBUNG |
|---|---|
200 | Group was updated |
400 | Bad request |
401 | Authorization failure |
403 | Permission denied |
404 | Resource not found |
409 | Duplicate record detected |
429 | Too many requests |
500 | Internal server error |
Codebeispiele
curl \
-X PUT \
-H "Accept: application/scim+json" \
-H "Authorization: Bearer <YOUR-TOKEN>" \
http(s)://HOSTNAME/api/v3/scim/v2/Groups/SCIM_GROUP_ID \
-d '{"schemas":["urn:ietf:params:scim:schemas:core:2.0:Group"],"externalId":"8aa1a0c0-c4c3-4bc0-b4a5-2ef676900159","displayName":"Engineering"}'Group was updated
Status: 200{
"schemas": [
"urn:ietf:params:scim:schemas:core:2.0:Group"
],
"id": "abcd27f8-a9aa-11ea-8221-f59b2be9cccc",
"externalId": "8aa1a0c0-c4c3-4bc0-b4a5-2ef676900159",
"displayName": "Engineering",
"members": [
{
"value": "879db59-3bdf-4490-ad68-ab880a2694745",
"$+ref": "https://api.github.localhost/scim/v2/Users/879db59-3bdf-4490-ad68-ab880a2694745",
"displayName": "User 1"
},
{
"value": "0db508eb-91e2-46e4-809c-30dcbda0c685",
"$+ref": "https://api.github.localhost/scim/v2/Users/0db508eb-91e2-46e4-809c-30dcbda0c685",
"displayName": "User 2"
}
],
"meta": {
"resourceType": "Group",
"created": "2012-03-27T19:59:26.000Z",
"lastModified": "2018-03-27T19:59:26.000Z",
"location": "https://api.github.localhost/scim/v2/Groups/927fa2c08dcb4a7fae9e"
}
}Update an attribute for a SCIM enterprise group
Note: The SCIM API endpoints for enterprise accounts are currently in private beta and are subject to change.
Update a provisioned group’s individual attributes.
To change a group’s values, you must provide a specific Operations JSON format that contains at least one of the add, remove, or replace operations. For examples and more information on the SCIM operations format, see the SCIM specification. Update can also be used to add group memberships.
Group memberships can be sent one at a time or in batches for faster performance. Note: The memberships are referenced through a local user id, and the user will need to be created before they are referenced here.
Parameter
| Headers | |||||||
|---|---|---|---|---|---|---|---|
| Name, Type, Description | |||||||
acceptstringSetting to | |||||||
| Path parameters | |||||||
| Name, Type, Description | |||||||
scim_group_idstringRequiredA unique identifier of the SCIM group. | |||||||
| Body parameters | |||||||
| Name, Type, Description | |||||||
Operationsarray of objectsRequiredpatch operations list | |||||||
Properties of | |||||||
| Name, Type, Description |
|---|
opstringRequiredCan be one of: |
pathstring |
valuestringCorresponding 'value' of that field specified by 'path' |
schemasarray of stringsRequiredHTTP-Antwortstatuscodes
| Statuscode | BESCHREIBUNG |
|---|---|
200 | Success, group was updated |
204 | No Content |
400 | Bad request |
401 | Authorization failure |
403 | Permission denied |
404 | Resource not found |
409 | Duplicate record detected |
429 | Too many requests |
500 | Internal server error |
Codebeispiele
curl \
-X PATCH \
-H "Accept: application/scim+json" \
-H "Authorization: Bearer <YOUR-TOKEN>" \
http(s)://HOSTNAME/api/v3/scim/v2/Groups/SCIM_GROUP_ID \
-d '{"schemas":["urn:ietf:params:scim:api:messages:2.0:PatchOp"],"Operations":[{"op":"replace","path":"displayName","value":"Employees"}]}'Success, group was updated
Status: 200{
"schemas": [
"urn:ietf:params:scim:schemas:core:2.0:Group"
],
"id": "abcd27f8-a9aa-11ea-8221-f59b2be9cccc",
"externalId": "8aa1a0c0-c4c3-4bc0-b4a5-2ef676900159",
"displayName": "Engineering",
"members": [
{
"value": "879db59-3bdf-4490-ad68-ab880a2694745",
"$+ref": "https://api.github.localhost/scim/v2/Users/879db59-3bdf-4490-ad68-ab880a2694745",
"displayName": "User 1"
},
{
"value": "0db508eb-91e2-46e4-809c-30dcbda0c685",
"$+ref": "https://api.github.localhost/scim/v2/Users/0db508eb-91e2-46e4-809c-30dcbda0c685",
"displayName": "User 2"
}
],
"meta": {
"resourceType": "Group",
"created": "2012-03-27T19:59:26.000Z",
"lastModified": "2018-03-27T19:59:26.000Z",
"location": "https://api.github.localhost/scim/v2/Groups/927fa2c08dcb4a7fae9e"
}
}Delete a SCIM group from an enterprise
Note: The SCIM API endpoints for enterprise accounts are currently in private beta and are subject to change.
Deletes a SCIM group from an enterprise.
Parameter
| Headers |
|---|
| Name, Type, Description |
acceptstringSetting to |
| Path parameters |
| Name, Type, Description |
scim_group_idstringRequiredA unique identifier of the SCIM group. |
HTTP-Antwortstatuscodes
| Statuscode | BESCHREIBUNG |
|---|---|
204 | Group was deleted, no content |
400 | Bad request |
401 | Authorization failure |
403 | Permission denied |
404 | Resource not found |
429 | Too many requests |
500 | Internal server error |
Codebeispiele
curl \
-X DELETE \
-H "Accept: application/vnd.github+json" \
-H "Authorization: Bearer <YOUR-TOKEN>" \
http(s)://HOSTNAME/api/v3/scim/v2/Groups/SCIM_GROUP_IDGroup was deleted, no content
Status: 204List SCIM provisioned identities for an enterprise
Note: The SCIM API endpoints for enterprise accounts are currently in private beta and are subject to change.
Lists provisioned SCIM enterprise members.
When a user with a SCIM-provisioned external identity is removed from an enterprise through a patch with active flag set to false, the account's metadata is preserved to allow the user to re-join the enterprise in the future. However, the user's account will be suspended and the user will not be able to sign-in. In order to permanently suspend the users account with no ability to re-join the enterprise in the future, use the delete request. Users that were not permanently deleted will be visible in the returned results.
You can improve query search time by using the excludedAttributes query parameter with a value of groups to exclude groups from the response.
Parameter
| Headers |
|---|
| Name, Type, Description |
acceptstringSetting to |
| Query parameters |
| Name, Type, Description |
filterstringIf specified, only results that match the specified filter will be returned. Multiple filters are not supported. Possible filters are |
excludedAttributesstringExcludes the specified attribute from being returned in the results. Using this parameter can speed up response time. |
startIndexintegerUsed for pagination: the starting index of the first result to return when paginating through values. Default: |
countintegerUsed for pagination: the number of results to return per page. Default: |
HTTP-Antwortstatuscodes
| Statuscode | BESCHREIBUNG |
|---|---|
200 | Success, either users were found or not found |
400 | Bad request |
401 | Authorization failure |
403 | Permission denied |
429 | Too many requests |
500 | Internal server error |
Codebeispiele
curl \
-H "Accept: application/scim+json" \
-H "Authorization: Bearer <YOUR-TOKEN>" \
http(s)://HOSTNAME/api/v3/scim/v2/UsersSuccess, either users were found or not found
Status: 200{
"schemas": [
"urn:ietf:params:scim:api:messages:2.0:ListResponse"
],
"totalResults": 1,
"Resources": [
{
"schemas": [
"urn:ietf:params:scim:schemas:core:2.0:User"
],
"externalId": "E012345",
"id": "7fce0092-d52e-4f76-b727-3955bd72c939",
"active": true,
"userName": "E012345",
"name": {
"formatted": "Ms. Mona Lisa Octocat",
"familyName": "Octocat",
"givenName": "Mona",
"middleName": "Lisa"
},
"displayName": "Mona Lisa",
"emails": [
{
"value": "mlisa@example.com",
"type": "work",
"primary": true
}
],
"roles": [
{
"value": "User",
"primary": false
}
]
}
],
"startIndex": 1,
"itemsPerPage": 20
}Provision a SCIM enterprise user
Note: The SCIM API endpoints for enterprise accounts are currently in private beta and are subject to change.
Creates an external identity for a new SCIM enterprise user.
SCIM does not authenticate users, it only provisions them. The authentication of users is done by SAML. However, when SCIM is enabled, all users need to be provisioned through SCIM before a user can sign in through SAML. The matching of a user to a SCIM provisioned user is done when the SAML assertion is consumed. The user will be matched on SAML response NameID to SCIM userName.
When converting existing enterprise to use SCIM, the user handle (userName) from the SCIM payload will be used to match the provisioned user to an already existing user in the enterprise. Since the new identity record is created for newly provisioned users the matching for those records is done using a user's handle. Currently the matching will be performed to all of the users no matter if they were SAML JIT provisioned or created as local users.
Parameter
| Headers | ||||||||
|---|---|---|---|---|---|---|---|---|
| Name, Type, Description | ||||||||
acceptstringSetting to | ||||||||
| Body parameters | ||||||||
| Name, Type, Description | ||||||||
schemasarray of stringsRequiredThe URIs that are used to indicate the namespaces of the SCIM schemas. | ||||||||
externalIdstringRequiredA unique identifier for the resource as defined by the provisioning client. | ||||||||
activebooleanRequiredWhether the user active in the IdP. | ||||||||
userNamestringRequiredThe username for the user. | ||||||||
nameobject | ||||||||
Properties of | ||||||||
| Name, Type, Description |
|---|
formattedstringThe full name, including all middle names, titles, and suffixes as appropriate, formatted for display. |
familyNamestringRequiredThe family name of the user. |
givenNamestringRequiredThe given name of the user. |
middleNamestringThe middle name(s) of the user. |
displayNamestringRequiredA human-readable name for the user.
emailsarray of objectsRequiredThe emails for the user.
Properties of emails
| Name, Type, Description |
|---|
valuestringRequiredThe email address. |
typestringRequiredThe type of email address. |
primarybooleanRequiredWhether this email address is the primary address. |
rolesarray of objectsThe roles assigned to the user.
Properties of roles
| Name, Type, Description |
|---|
displaystring |
typestring |
valuestringRequiredThe role value representing a user role in GitHub. Can be one of: |
primarybooleanIs the role a primary role for the user. |
HTTP-Antwortstatuscodes
| Statuscode | BESCHREIBUNG |
|---|---|
201 | User has been created |
400 | Bad request |
401 | Authorization failure |
403 | Permission denied |
409 | Duplicate record detected |
429 | Too many requests |
500 | Internal server error |
Codebeispiele
curl \
-X POST \
-H "Accept: application/scim+json" \
-H "Authorization: Bearer <YOUR-TOKEN>" \
http(s)://HOSTNAME/api/v3/scim/v2/Users \
-d '{"schemas":["urn:ietf:params:scim:schemas:core:2.0:User"],"externalId":"E012345","active":true,"userName":"E012345","name":{"formatted":"Ms. Mona Lisa Octocat","familyName":"Octocat","givenName":"Mona","middleName":"Lisa"},"displayName":"Mona Lisa","emails":[{"value":"mlisa@example.com","type":"work","primary":true}],"roles":[{"value":"User","primary":false}]}'User has been created
Status: 201{
"schemas": [
"urn:ietf:params:scim:schemas:core:2.0:User"
],
"id": "7fce0092-d52e-4f76-b727-3955bd72c939",
"externalId": "E012345",
"active": true,
"userName": "E012345",
"name": {
"formatted": "Ms. Mona Lisa Octocat",
"familyName": "Octocat",
"givenName": "Mona",
"middleName": "Lisa"
},
"displayName": "Mona Lisa",
"emails": [
{
"value": "mlisa@example.com",
"type": "work",
"primary": true
}
],
"roles": [
{
"value": "User",
"primary": false
}
],
"meta": {
"resourceType": "User",
"created": "2012-03-27T19:59:26.000Z",
"lastModified": "2018-03-27T19:59:26.000Z",
"location": "https://api.github.localhost/scim/v2/Users/7fce0092-d52e-4f76-b727-3955bd72c939"
}
}Get SCIM provisioning information for an enterprise user
Note: The SCIM API endpoints for enterprise accounts are currently in private beta and are subject to change.
Gets information about a SCIM user.
Parameter
| Headers |
|---|
| Name, Type, Description |
acceptstringSetting to |
| Path parameters |
| Name, Type, Description |
scim_user_idstringRequiredThe unique identifier of the SCIM user. |
HTTP-Antwortstatuscodes
| Statuscode | BESCHREIBUNG |
|---|---|
200 | Success, a user was found |
400 | Bad request |
401 | Authorization failure |
403 | Permission denied |
404 | Resource not found |
429 | Too many requests |
500 | Internal server error |
Codebeispiele
curl \
-H "Accept: application/scim+json" \
-H "Authorization: Bearer <YOUR-TOKEN>" \
http(s)://HOSTNAME/api/v3/scim/v2/Users/SCIM_USER_IDSuccess, a user was found
Status: 200{
"schemas": [
"urn:ietf:params:scim:schemas:core:2.0:User"
],
"id": "7fce0092-d52e-4f76-b727-3955bd72c939",
"externalId": "E012345",
"active": true,
"userName": "E012345",
"name": {
"formatted": "Ms. Mona Lisa Octocat",
"familyName": "Octocat",
"givenName": "Mona",
"middleName": "Lisa"
},
"displayName": "Mona Lisa",
"emails": [
{
"value": "mlisa@example.com",
"type": "work",
"primary": true
}
],
"roles": [
{
"value": "User",
"primary": false
}
],
"meta": {
"resourceType": "User",
"created": "2012-03-27T19:59:26.000Z",
"lastModified": "2018-03-27T19:59:26.000Z",
"location": "https://api.github.localhost/scim/v2/Users/7fce0092-d52e-4f76-b727-3955bd72c939"
}
}Set SCIM information for a provisioned enterprise user
Note: The SCIM API endpoints for enterprise accounts are currently in private beta and are subject to change.
Replaces an existing provisioned user's information.
You must provide all the information required for the user as if you were provisioning them for the first time. Any existing user information that you don't provide will be removed. If you want to only update a specific attribute, use the Update an attribute for a SCIM user endpoint instead.
Warning: Setting active: false will suspend a user and obfuscate the user handle and user email. Since the implementation is a generic SCIM implementation and does not differentiate yet between different IdP providers, for Okta, the user GDPR data will not be purged and the credentials will not be removed.
Parameter
| Headers | ||||||||
|---|---|---|---|---|---|---|---|---|
| Name, Type, Description | ||||||||
acceptstringSetting to | ||||||||
| Path parameters | ||||||||
| Name, Type, Description | ||||||||
scim_user_idstringRequiredThe unique identifier of the SCIM user. | ||||||||
| Body parameters | ||||||||
| Name, Type, Description | ||||||||
schemasarray of stringsRequiredThe URIs that are used to indicate the namespaces of the SCIM schemas. | ||||||||
externalIdstringRequiredA unique identifier for the resource as defined by the provisioning client. | ||||||||
activebooleanRequiredWhether the user active in the IdP. | ||||||||
userNamestringRequiredThe username for the user. | ||||||||
nameobject | ||||||||
Properties of | ||||||||
| Name, Type, Description |
|---|
formattedstringThe full name, including all middle names, titles, and suffixes as appropriate, formatted for display. |
familyNamestringRequiredThe family name of the user. |
givenNamestringRequiredThe given name of the user. |
middleNamestringThe middle name(s) of the user. |
displayNamestringRequiredA human-readable name for the user.
emailsarray of objectsRequiredThe emails for the user.
Properties of emails
| Name, Type, Description |
|---|
valuestringRequiredThe email address. |
typestringRequiredThe type of email address. |
primarybooleanRequiredWhether this email address is the primary address. |
rolesarray of objectsThe roles assigned to the user.
Properties of roles
| Name, Type, Description |
|---|
displaystring |
typestring |
valuestringRequiredThe role value representing a user role in GitHub. Can be one of: |
primarybooleanIs the role a primary role for the user. |
HTTP-Antwortstatuscodes
| Statuscode | BESCHREIBUNG |
|---|---|
200 | User was updated |
400 | Bad request |
401 | Authorization failure |
403 | Permission denied |
404 | Resource not found |
409 | Duplicate record detected |
429 | Too many requests |
500 | Internal server error |
Codebeispiele
curl \
-X PUT \
-H "Accept: application/scim+json" \
-H "Authorization: Bearer <YOUR-TOKEN>" \
http(s)://HOSTNAME/api/v3/scim/v2/Users/SCIM_USER_ID \
-d '{"schemas":["urn:ietf:params:scim:schemas:core:2.0:User"],"externalId":"E012345","active":true,"userName":"E012345","name":{"formatted":"Ms. Mona Lisa Octocat","familyName":"Octocat","givenName":"Mona","middleName":"Lisa"},"displayName":"Mona Lisa","emails":[{"value":"mlisa@example.com","type":"work","primary":true}],"roles":[{"value":"User","primary":false}]}'User was updated
Status: 200{
"schemas": [
"urn:ietf:params:scim:schemas:core:2.0:User"
],
"id": "7fce0092-d52e-4f76-b727-3955bd72c939",
"externalId": "E012345",
"active": true,
"userName": "E012345",
"name": {
"formatted": "Ms. Mona Lisa Octocat",
"familyName": "Octocat",
"givenName": "Mona",
"middleName": "Lisa"
},
"displayName": "Mona Lisa",
"emails": [
{
"value": "mlisa@example.com",
"type": "work",
"primary": true
}
],
"roles": [
{
"value": "User",
"primary": false
}
],
"meta": {
"resourceType": "User",
"created": "2012-03-27T19:59:26.000Z",
"lastModified": "2018-03-27T19:59:26.000Z",
"location": "https://api.github.localhost/scim/v2/Users/7fce0092-d52e-4f76-b727-3955bd72c939"
}
}Update an attribute for a SCIM enterprise user
Note: The SCIM API endpoints for enterprise accounts are currently in private beta and are subject to change.
Update a provisioned user's individual attributes.
To change a user's values, you must provide a specific Operations JSON format that contains at least one of the add, remove, or replace operations. For examples and more information on the SCIM operations format, see the SCIM specification.
Note: Complicated SCIM path selectors that include filters are not supported. For example, a path selector defined as "path": "emails[type eq \"work\"]" will not work.
Warning: Setting active: false will suspend a user and obfuscate the user handle and user email. Since the implementation is a generic SCIM implementation and does not differentiate yet between different IdP providers, for Okta, the user GDPR data will not be purged and the credentials will not be removed.
{
"Operations":[{
"op":"replace",
"value":{
"active":false
}
}]
}
Parameter
| Headers | |||||||
|---|---|---|---|---|---|---|---|
| Name, Type, Description | |||||||
acceptstringSetting to | |||||||
| Path parameters | |||||||
| Name, Type, Description | |||||||
scim_user_idstringRequiredThe unique identifier of the SCIM user. | |||||||
| Body parameters | |||||||
| Name, Type, Description | |||||||
Operationsarray of objectsRequiredpatch operations list | |||||||
Properties of | |||||||
| Name, Type, Description |
|---|
opstringRequiredCan be one of: |
pathstring |
valuestringCorresponding 'value' of that field specified by 'path' |
schemasarray of stringsRequiredHTTP-Antwortstatuscodes
| Statuscode | BESCHREIBUNG |
|---|---|
200 | Success, user was updated |
400 | Bad request |
401 | Authorization failure |
403 | Permission denied |
404 | Resource not found |
409 | Duplicate record detected |
429 | Too many requests |
500 | Internal server error |
Codebeispiele
curl \
-X PATCH \
-H "Accept: application/scim+json" \
-H "Authorization: Bearer <YOUR-TOKEN>" \
http(s)://HOSTNAME/api/v3/scim/v2/Users/SCIM_USER_ID \
-d '{"schemas":["urn:ietf:params:scim:api:messages:2.0:PatchOp"],"Operations":[{"op":"replace","path":"emails[type eq '\''work'\''].value","value":"updatedEmail@microsoft.com"},{"op":"replace","path":"name.familyName","value":"updatedFamilyName"}]}'Success, user was updated
Status: 200{
"schemas": [
"urn:ietf:params:scim:schemas:core:2.0:User"
],
"id": "7fce0092-d52e-4f76-b727-3955bd72c939",
"externalId": "E012345",
"active": true,
"userName": "E012345",
"name": {
"formatted": "Ms. Mona Lisa Octocat",
"familyName": "Octocat",
"givenName": "Mona",
"middleName": "Lisa"
},
"displayName": "Mona Lisa",
"emails": [
{
"value": "mlisa@example.com",
"type": "work",
"primary": true
}
],
"roles": [
{
"value": "User",
"primary": false
}
],
"meta": {
"resourceType": "User",
"created": "2012-03-27T19:59:26.000Z",
"lastModified": "2018-03-27T19:59:26.000Z",
"location": "https://api.github.localhost/scim/v2/Users/7fce0092-d52e-4f76-b727-3955bd72c939"
}
}Delete a SCIM user from an enterprise
Note: The SCIM API endpoints for enterprise accounts are currently in private beta and are subject to change.
Permanently suspends a SCIM user from an enterprise, removes all data for the user, obfuscates the login, email, and display name of the user, removes all external-identity SCIM attributes, and deletes the emails, avatar, PATs, SSH keys, OAuth authorizations credentials, GPG keys, and SAML mappings for the user. You will not be able to undo this action.
Parameter
| Headers |
|---|
| Name, Type, Description |
acceptstringSetting to |
| Path parameters |
| Name, Type, Description |
scim_user_idstringRequiredThe unique identifier of the SCIM user. |
HTTP-Antwortstatuscodes
| Statuscode | BESCHREIBUNG |
|---|---|
204 | User was deleted, no content |
400 | Bad request |
401 | Authorization failure |
403 | Permission denied |
404 | Resource not found |
429 | Too many requests |
500 | Internal server error |
Codebeispiele
curl \
-X DELETE \
-H "Accept: application/vnd.github+json" \
-H "Authorization: Bearer <YOUR-TOKEN>" \
http(s)://HOSTNAME/api/v3/scim/v2/Users/SCIM_USER_IDUser was deleted, no content
Status: 204
