11.3 REST GitHub Collectors

Like the other OpenText Identity Governance collectors, the REST GitHub collectors map accounts and permissions to identities by association or other attributes. To successfully map accounts and permissions to identities, identities must be collected using the identity source that is configured in the GIT server. The REST GitHub permission collector collects all organizations, teams, repositories, the permission to permission association, and also the holder association. The collector has a batch size limit of 100 records.

The REST GitHub collector template includes mandatory attribute mappings suitable for the target application. However, you can configure other attributes and then edit the transform script to build the required payload. For example, for GitHub accounts, if you want to map ‘email’ for the Account-User Mapping attribute, you need to map Account-User Mapping with user and write the script as follows to parse the email from the user JSON:

var user = JSON.parse(inputValue) outputValue = user['email'];

Apart from the mapped attributes, you can add additional attributes for organization, teams, and repository by parsing values from the organization, teams, or repository JSONs.

If you use Cloud Bridge to collect data from your on-premises data centers, you must specify ordinals for the respective authentication method in the Cloud Bridge user interface (http://localhost (CBA IP address or DNS name):8080).