Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

1. Locate your desired Github application instance on Zilla, click Sync now in the top right and enable API Integration. Find the Client Id and Secret you obtained in the last step and enter them into the corresponding boxes. For Organization Id, enter the username of your organization on Github (located at Your Organizations tab when you click profile image at upper right corner). For "Sync repositories as resource permissions", choose Yes if the integration should sync user access for each repository within the organization. This option results in additional Repository Role permissions in the Available Permissions.

Info

Note:

  1. When updating the “Sync repositories as resource permissions” setting from No to Yes, you must revoke all user tokens in Github.

  2. If you are trying to sync GitHub’s Enterprise Server into Zilla then you have to add your domain as config otherwise leave it blank.

...

...

Image Modified

If “Sync repositories as resource permissions” is Yes, on the Permissions tab additional permissions are displayed for each account (e.g., “admin: repo1“, “maintain: repo2”, “read: repo3”, “triage: repo4”, “write: repo5”).

...

4. Once complete you may view the data on Zilla.

Info

Troubleshooting GitHub Integration:

  1. Error 401 - This could due to expired access token or the user trying to sync does not have admin or owner access to GitHub’s account. Try reauthenticating the GitHub instance will resolve the error and if the issue still persist contact your admin for right access.

  2. Error 403 - This error could be due to insufficient scopes, please ensure that the scopes provided for zilla connector should be same as mentioned in these document. Error 403 could also occur if the organization has enabled OAuth App Access Restrictions, disabling the restriction would fix the issue. Refer this document for disabling the OAuth app access restrictions.

  3. Error 422 - This could also occur because your organization has enabled OAuth App Access Restrictions. Refer this document for disabling the OAuth app access restrictions.

  4. Error 400 - This could be due to API error please contact support@zillasecurity.com.

Include Page
Integrations Footer
Integrations Footer