Hello all,
I have configured the source using Github saas connector in IDN. When I configured it the test connection and account aggregation were working fine,but now when I am testing it is giving me below error -
I have asked Sailpoint team to provide the logs to understand the issue.I yet to receive it. Meanwhile any idea why I am getting this error.I kept 10 as page size and the number of accounts present in source are around 418.
wait for some time and try again.
I tried to run the next aggregation post 30 min to 1 hour ,also I am trying to do it next day.But same issue it is showing.
Hi Priyanka,
That’s a frustrating error to encounter, especially when it was working previously.
The error message is quite telling. It indicates that the connector’s underlying process unexpectedly terminated while trying to communicate back to ISC. This isn’t a GitHub API error directly, but rather an issue with the connector’s runtime environment allocated to your tenant.
For the record I have GitHub OOTB connector configured and did an account aggregation just now, running fine. Try enabling debug and sharing logs from SailPoint CLI using command sail conn logs tail
for account aggregation: -
Good luck
show this error to GitHub admin, here it tells SAML idp is disabled or misconfigured at GitHub level, Get valid access token to retest please.
Hi Priyanka,
Seems like the SAML SSO was enabled for the GitHub Organization you are connected to after configuration. See if you can or the dev team using GitHub Organization agree to update/bypass SSO for the account that you are using for PAT for authentication. Alternatively a new service account with required permission can be created like a normal GitHub user with permission to the GitHub Org.
Good luck
I have raised Sailpoint support case, and the team is internally checking.
You might not get a resolution you are looking for with support as the the OOTB connector is working fine. Checking internally is the way I believe.
Hi @TheOneAMSheriff ,
The Github have checked at there end the configuration looks good what else we need to check on our end?
I will suggest please delete the source and re-create it.
I tried to configure it, but same error I am getting.