Working with Private Repos and PATs

[PatrickCaneloDigital]

Select Topic Area

Question

Body

Has anyone successfully worked with Private Repos (https://) and access keys?
I know, ideal would be the ssh approach and locally I use that too, but on one of my hosting I cannot add ssh certificates, so the best apparent option would be PAT

But PATs on private repos seems to work very badly as URLs take a username/password approach and thus get later blocked.

Yesterday I was able to somehow clone a repo with a PAT, but today as I tried a pull request I was asked for a password.

git pull
> Enter Password for https://MyToken@github.com/MyAccountName/myrepo.git
Password for 'https://github_mytoken@github.com': 
remote: Support for password authentication was removed on August 13, 2021.

So the PAT (even if expiration is in one year) somehow was valid only for a one time access.

So I deleted the repo (clone seemed to work, I tried to reclone it)

git clone https://MyTokenName:MyToken@github.com/MyAccountName/myrepo.git
Cloning into 'myrepo'...
remote: Support for password authentication was removed on August 13, 2021.

Any combination using only the token gives the same error, at latest in the second access:

git clone https://MyToken@github.com/MyAccountName/myrepo.git
Cloning into 'myrepo'...
Password for 'https://MyToken@github.com': 
remote: Support for password authentication was removed on August 13, 2021.

My actual conclusion is that PAT in that form is simply not useable for private repos...
The ssh method would be if I'd be able to use ssh-add on my hosting, but I'm not...

[shinybrightstar]

Welcome to the GitHub Community, @PatrickCaneloDigital, we're happy you're here! You are more likely to get a useful response if you are posting your question in the applicable category and are explicit about what your project entails--giving a few more details might help someone give you a nudge in the right direction. I've gone ahead and moved it for you. Good luck!