We have GitHub Cloud Enterprise with Managed accounts. We created a service account and I was able to login to SonarCloud using that particular account. However, when I try to import our organization I get a 404 Not-Found on the GitHub link.
Is this a permission issue or are managed accounts not supported in SonarCloud?
Would creating the organization manually make any difference?
Thank you for the reply, I doubt this is the issue as we have tried now with two different accounts and I tried with two different computers and got the same result. I also checked with our network team and they don’t believe this to be the issue.
I get the 404 for a url similar to this https://github.com/organizations/orgid/settings/installations/1234567
orgid is our organization and the is a number at the end.
Any other suggestions? Should I create the organization manually and only use CI scanning?
Even if the account doesn’t have permission to install applications, you should be routed through a path where you can request from an admin that the application is installed.
I’m going to flag this for attention, as I’m not sure what’s going on.
Sorry for the late answer. I can’t try myself with a managed account so I can’t confirm that it’s how it should behave, however it looks that it is expected.
Cannot install GitHub Apps on their user accounts.
Can install GitHub Apps on a repository if the app doesn’t request organization permissions and if the managed user account has admin access to the repository.
Can install GitHub Apps on an organization if the managed user account is an organization owner.
Can create GitHub Apps and OAuth apps.
I’m guessing that your account doesn’t have permissions to install App on the org and even if what Colin’s said is true:
Even if the account doesn’t have permission to install applications, you should be routed through a path where you can request from an admin that the application is installed.
I’m wondering if that’s true for managed users as well (this is GitHub features, we’re not expert about them).
Do you have a way to try to do the same with the organization owner? As the doc says “if the managed user account is an organization owner”, I would expect this to work.
Hello @Antoine, one of the enterprise owners did try but got the same 404.
We were wondering if there is a way to schedule a session to make sure we are doing everything correctly, or would this be something we should be reaching out to GitHub to get resolved?