SSH login requires "enable SSO" which does not exist

I just know this going to get me flamed (with RTFM) but I just created a githib account. I want to push my repo to it so I used the URL

git remote add origin https://github.com//
Got password prompt …several steps later …

Beginning August 13, 2021, we will no longer accept account passwords when authenticating Git operations

So looked at setting up SSH access. Added my public key. Manage to get through the test

(here but I’m not allowed to post URL) /en/github/authenticating-to-github/connecting-to-github-with-ssh/testing-your-ssh-connection

ie: $ ssh -T git@github.com

So back to my original

git push --set-upstream origin master

But again prompted for password, so RTFM

(here but I’m not allowed to post URL)/en/github/authenticating-to-github/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on

and it says … “Enable SSO” …but there is no such button.

Have passwords been disabled but the replacement feature not enabled for mortal users?

That sounds like the repository URL still uses HTTPS, not SSH. You can check the URL with:

git remote show origin

If there are still https://github.com/... URLs, you can change to SSH with the following command. Replace the URL with that for your repository, the pattern should be the same.

git remote set-url origin git@github.com:user/repo.git

Thank you it was indeed that. I discovered by battering my head against it repeatedly .

The user experience was very poor. I setup the URL as per instructions, then got a message saying that “password access” had been suspended (as a method) and I had to use SSH or some kind of access token. Very happy to use SSH (preferable in fact)

A better approach would have been, "We no longer support xxxx (e.g. password authentication) you need to switch to methodA or methodB

+guide to setting up methodA,
+guide to switching from current-method to methodA

ie it was perfectly possible they could have used HTTPS but required me to authenticate using SSH . On reflection that way they’ve done it is more sensible/standard …I just wish they’d told me!

Anyhow thanks for your help. Hopefully it will help future users (with that in mind, I’ll add some keywords)

password access, ssh access, SSH login, git-URL