Recursive Clone With Repo Authentication Token

[Adam]

I am attempting to clone a repository - containing several submodules - to a shared PC.  I have created authentication tokens for each repository.  When I enter any command requiring user authentication the Atlassian/Bitbucket authentication window appears.


Entering my personal account credential triggers an SSO event.  I want to avoid this due to the shared nature of the PC.  Entering the bot email (@bots.bitbucket.org) and the associated access token causes the authentication to fail.  

Is there a special git syntax that must be used to trigger the use of the authentication token? Why can't I use the bot account and token to login?  

Any assistance or guidance would be appreciated. 

[Mark C]

Hi @Adam

Welcome to the community.

Could you try to clear your credential manager first and try to authenticate again and see if that works?
Alternatively, you can also try to use an SSH connection instead and this will avoid using tokens entirely for your repository and submodules.

Regards,
Mark C