Why a workspace member can access one repo bot not another?

[Mirko Tebaldi]

We have a workspace with 2 projects

We invited as developer a new coworker. He accepted.

He clones succesfully the first project.

The first project has a dependency to the 2nd project in the same workspace in composer.json 

When doing composer install, composer complains because user has no access rights to 2nd repository.

Trying to do a normal git clone it works.

What could be happening!?

[Caroline R]

Hi, @Mirko Tebaldi, thank you for reaching out to Atlassian Community.

Since you mentioned the dev was able to clone this repo, I understand that they have access to both repositories, is that correct? 

If that's the case, could you please confirm what URL they have for the second repo in composer configuration (is it HTTPS or SSH)? I’m not very familiar with composer, so can you confirm if they have set up authentication for these repos and how?

Please feel free to share any additional information that might help us in this case.

Kind regards,
Caroline