search

3rd-party-integrations / github-team-sync

Sync GitHub teams to groups in Active Directory, LDAP, Okta, OneLogin or AzureAD when using any authentication method for GitHub.
MIT License
201 stars 67 forks source link

LDAP requirement #146

Closed oobeLachlan closed 1 year ago

oobeLachlan commented 2 years ago

Please add guidance for GHES running in Azure to use this without requiring LDAP via AADDS.

https://learn.microsoft.com/en-us/azure/active-directory/fundamentals/auth-ldap

Can't use AAD User Provisioning either because of Github SCIM API requirement.

https://learn.microsoft.com/en-us/azure/active-directory/saas-apps/github-provisioning-tutorial

primetheus commented 1 year ago

Please add guidance for GHES running in Azure to use this without requiring LDAP via AADDS. https://learn.microsoft.com/en-us/azure/active-directory/fundamentals/auth-ldap

@oobeLachlan thank you for opening this issue! There is currently an example environment file for running AzureAD without LDAP (.env.example.aad), and it makes use of msal to authenticate. If you use this configuration it will be SAML rather than LDAP.

Can't use AAD User Provisioning either because of Github SCIM API requirement. https://learn.microsoft.com/en-us/azure/active-directory/saas-apps/github-provisioning-tutorial

This tool will only handle user creation if your GHES instance is configured with Local authentication. Otherwise you will need to leverage the GitHub native feature for user provisioning. The main purpose of this utility is to synchronize GitHub Team membership with users in groups within your directory. In other words, the users should already exist in GitHub and be provisioned through some other means.

primetheus commented 1 year ago

@oobeLachlan if you still need help with this, please feel free to reach back out