nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Why can't a user designated as an Admin push to a repo?

Fred Fierling_tovn8e

I want a user to have read-only access to a repo and be able to clone it so that he can push changes to the clone. I've given him Admin perms for the cloned repo. He can pull from it, but he can't push to it. He has no other perms (workspace or project). Can this work? If not, what has to be added?

Unauthorized

debug1: channel 0: free: client-session, nchannels 1

Transferred: sent 3760, received 2424 bytes, in 0.2 seconds

Bytes per second: sent 18473.2, received 11909.3

debug1: Exit status 1

fatal: Could not read from remote repository.

Please make sure you have the correct access rights

and the repository exists.

Accepted answers

Mark C

Hi @Fred Fierling

Thank you for reaching out to the community.

Could you confirm if the use is using SSH or HTTPS connection while cloning/pushing to the repository?

Also, the "Unauthorized" error is likely related to authentication permissions.

If the user is using an App password, you can refer to this existing knowledge-based article that might help: Error message 401: Unauthorized/Invalid Credentials in Visual Studio Bitbucket Cloud Extension

Regards,
Mark C

All comments

Mark C

Hi @Fred Fierling

Thank you for reaching out to the community.

Could you confirm if the use is using SSH or HTTPS connection while cloning/pushing to the repository?

Also, the "Unauthorized" error is likely related to authentication permissions.

Fred Fierling_tovn8e

The user is using SSH. His public key was configured in the repo's Access Keys.

This page has "Use access keys to gain read-only access to this repository." so we also tried giving him Admin perms in the Project Access Keys and even for the workspace. No joy.

Mark C

Hi @Fred Fierling

Could you try removing the SSH key from the repo's Access keys and then ask the user to add it to their personal SSH key settings? - https://bitbucket.org/account/settings/ssh-keys/

After that, give admin permission to the user.

Let's see what happens after that.

Regards,
Mark C

Fred Fierling_tovn8e

That's the trick.

Thanks,

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

bitbucket

bitbucket-cloud