GitHub Team Entitlement Connector
Last Updated:
July 29th, 2024
We’ve recently announced a new GitHub Team connector using Entitlement Management!
If you have not seen the new application please locate it in your OIN Catalog. As with all other Entitlement Management connectors, make sure to enable Governance Engine first before enabling provisioning to take advantage of the new GitHub Team features.
The following provisioning features are supported:
- Import New Users
New users created in the third-party application will be downloaded and turned into new AppUser objects, for matching against existing OKTA users. - Push New Users
New users created through OKTA will also be created in the third-party application. - Push Profile Updates
Updates made to the user's profile through OKTA will be pushed to the third party application. - Push User Deactivation
Deactivating the user through OKTA will remove the user from the organization and all teams in the third-party application. - Reactivate Users
Reactivating the user through OKTA will add the user back to the organization and selected teams in the third-party application.
Don’t forget to configure the new connector and start taking advantage of GitHub and Entitlements Management.
More information is available here.
Happy Governing!
Related References
Training:
We’ve put together other resources below that can help you as you become familiar with Okta Identity Governance:
- We share two videos about Access Certification campaigns and Access Request in this article: Okta Identity Governance
- Corporate blog: Okta Identity Governance: A Unified IAM and Governance Solution
- How to Grant entitlements via API
- Guide on how to use the Okta Identity Governance API’s
Learn about the new capabilities available, Access Requests, Access Certifications, and more in this FAQ: Identity Governance FAQs
Limitations:
