-
Suggestion
-
Resolution: Unresolved
-
None
-
4
-
Issue Summary
Steps to Reproduce
- To reproduce that issue it's need to have github cloud organisation managed by Azure service - managed users.
Expected Results
- Organisations managed by Id Provider can link DVCS to github and sync repositories
Actual Results
- Customer has Github Enterprise Managed Users which means all GitHub accounts are managed by an IDP and are not publicly visible on github.com. This feature seems quite new (see here), so it's likely more customers will have this issue in the future.
- The integration works with a "normal" public user account on github.com, but not with Github Enterprise Managed Users. Error received is "Invalid user/team account".
- The error in the log is:
Unable to retrieve account information. hostUrl: https://github.com, account: {organisation_name} Not Found (404)
- The same 404 error can be reproduced when accessing the account directly on GitHub (example: https://github.com/{organisation_name})
- The same issue exists when trying to use an organization instead of a user for the integration.
Workaround
The workaround is to use the “dvcs.connector.github.user.validation.disabled” flag which disables pre-username validation. More details on how to disable a dark feature flag can be found here.
- causes
-
GHS-236775 You do not have permission to view this issue
-
THOR-197 You do not have permission to view this issue
- links to
Form Name |
---|
38f3cf3bb67b fb78a00798c3 atlassian-11
Hello Atlssian Team, is this workaround will be addressed in future releases? What is the plan to provide this feature support?
This is now the common way how GitHub Orgs are managed, it is better to have solution in-build with in the product itself.
Thank you for support.