Account Aggregation Issue - GitHub Enterprise SaaS Connector

Identity Security Cloud (ISC) ISC Discussion and Questions
,
1

Hi everyone,

I’m attempting to setup the (not superbly documented) delivered GitHub Enterprise SaaS connector and am running into an issue I hope folks can assist with.

Initial connectivity to (one) of our GitHub orgs is tested and working. Initial aggregation for entitlements for that org was successful: we see the expected roles and groups in Sailpoint. Initial aggregation for accounts, however is failing with the following error message:

[ConnectorError] Account aggregation failed. Cannot read properties of null (reading 'externalIdentities') (requestId: 1c17b091c6314c938f169490d298b1c3)

Sailpoint and GitHub documentation is not particularly helpful with regard to this error, so I’m hoping the community has some advice. Some specifics about our GitHub:

  • We’re using GitHub Enterprise managed users. Users attached to our orgs are being provisioned via SCIM with specific enterprise roles.
  • No external identities have access to repos in any of our orgs.

Any pointers on where to start looking would be greatly appreciated!

2

decrease page size in aggregation settings from 100 to 70 like that and try again.

3

Settiing the value to something lower, even as low as 10, gives the same error. I’ll note, there are very few accounts in this Enterprise at the moment (~10), as we are currently testing the migration of user accounts as GitHub Enterprise managed users.

4

in SandBox or test env please try this

[
{
“op”: “add”,
“path”: “/connectorAttributes/maxRetryCount”,
“value”: 5
},
{
“op”: “add”,
“path”: “/connectorAttributes/retryWaitTime”,
“value”: 60000
},
{
“op”: “add”,
“path”: “/connectorAttributes/retryableErrors”,
“value”: [
“Service Unavailable”,
“ConnectorError”,
“RuntimeException”
]
}
]

5

Hi Developers,
Same issue encountered with us also while doing account aggregation. @Colin could you please check this issue.

6

Hi @bussdw - It seems like while the aggregation is taking place, it is encountering a missing account object. Can you review the account schema of your problem source to see what’s marked as an account ID and account Name? Then, check if on the target GitHub org if the users have that particular attribute configured.

To debug this, try to manually make a GitHub GraphQL API call to get all users, look at the account attributes for the first few and check if you see any abnormalities. If you find any account schema attribute (as seen on ISC) missing, perhaps that’s where the problem is originating.

Also compare the same API response with your other successful org by running it there. If the comparison highlights a difference in data availability, you might want to check why the two differ.

Additionally, confirm if the service account used in integration on both orgs share the same set of permissions.