removing third-party app restriction worked for me.
https://github.com/organizations/YOUR_ORGANIZATION/settings/oauth_application_policy
Share and learn in the Docker community.
removing third-party app restriction worked for me.
https://github.com/organizations/YOUR_ORGANIZATION/settings/oauth_application_policy
Itās 2019 and this issue from 2015 is still unresolved. None of the recommended solutions here work either- Iāve unlinked and relinked my account multiple times, made sure the āthird party app restrictionā was enabled for docker hub, and I still canāt get the organization to show up in the new repository page.
Iām having the same problem, too. None of the methods mentioned above worked for me.
Thank you kizbitz for help us, your response fix this problem.
I am trying to create a āservice userā as per the documentation, but Iām really having trouble with this point. Iāve followed these directions:
After trying this multiple times combined with logging out and logging in, I still am unable to access my organizationās repository. @kitzbitz, is there any solution?
Edit: the solution was to make the āservice userā an OWNER of the repository and not just have write or maintenance permissions.
To be fair, this is present in the documentation:
This service account should have access to any repositories to be built, and must have administrative access to the source code repositories so it can manage deploy keys. If needed, you can limit this account to only a specific set of repositories required for a specific build.
It might be that I am alone in my misinterpretation, but there are a couple of reasons why I did not see ownership as a requirement:
This transition was bad for my dyslexia: "... so it can manage deploy keys. If needed, you can..."
I had mentally switched the full stop and comma so that it read "... so it can manage deploy keys, if needed. You can..."
If you read the two sentences and flip the comma and full stop like I did, it suggests that the administrative access is only needed if you explicitly want deploy keys (to where? I though maybe back to GitHub).
I think the documentation could be improved a bit to avoid this mistake:
This service account
shouldmust have access to any DockerHub repositories to be built, andmust haveadministrative access to the source code repositories so it can manage deploy keys.If neededyYou can also optionally limit this account to only a specific set of repositories required for a specific build.
This clarifies what is required and what is optional.
Same problem - I am unable to see all of the organizations I am a member of, even those where I am a public member. I also notice that for some organizations I am unable to see all of the public repositories in that organization.
Further, looking at the dev console, I see a lot of redā¦ I submitted a ticket to Support.