How do I premanently store the auto-generated password (AKA token)

Hi, ALL,

How do I “permanently” store the Auto-Generated Password (AKA token) on my machine for use.
My understanding is that it will go away every year hence the quotes, no matter whether it is compromised or not.

Because nobody will remember a bunch of nonsence to get to the github…

Thank you.

Do you mean a Personal Access Token (PAT)? The general recommendation is to store it in a password manager. I personally like KeePassXC.

And according to the documentation a PAT becomes invalid if it hasn’t been used for a year, not unconditionally.

@airtower-luna

Do you mean a Personal Access Token (PAT)? The general recommendation is to store it in a password > manager. I personally like KeePassXC.

No, I mean the autol-generated password (AKA token).
The token is when I have a CAC. The token is when I have a special device that generates a token. A token is when I have an application that generates a token. This is an autogenerated password. Nothing more, nothing less.

Now, what I wouold like to do is to have it saved on all 3 of my machies OSes. I have 3 laptops with Windows 8.1, Linux (both GNOME and KDE) and a Mac. I also have a VM with Windows 10.
And I need to store it somewhere so the GitHub access it everytime I try to push/pull the code without me interfering.

As I said - nobody in their right mind will remember a bunch of garbage. Unless of course you are a Wolfe Messing. :wink:

And according to the documentation a PAT becomes invalid if it hasn’t been used for a year, not > unconditionally.

My understanding is that every year the token will have to be refreshed.
Or GitHub devs already changing their policy?

Thank you.

That sounds to me like you’re using “token” in a way that’s different from what it usually means in a GitHub context. Could you explain exactly what you mean? Possibly related to 2FA, like a TOTP code?

Hi,
I do use the CAC tokens at work, but this is besides the point.
What GitHub propose is the autogenerated password and not a token whatever they want to call it. They can call it a UFO for all I care. But from the computer world POV, this is NOT a token.

Now I want a mean to store it somewhere on all of my machines, so that I won’t enter it every time I need to push/pull the updates to my code.
Because nobody, me and you included can remember a bunch of nonsense 24/7.

Do you know how to save this autogenerated password somewhere so that git client on windows/Linux/Mac can automatically log me in?

Anybody?
I don’t want to keep arguing about the terminology - this point is mute and GitHub can call iot whatever they want - even a “ufo” for all I care.

I just want to know how to store it on my machine so that it will be automatically picked up by the client.

Thank you.

So, now wonder how people will save their “tokens”?

Or they will keep entering it from the keyboard?

How do you guys expect people to work with GitHub?

Anyone?

I guess people are waiting till the very end to generate their “tokens” and save them locally on their machine.