-
Notifications
You must be signed in to change notification settings - Fork 875
feat: tokens #4380
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: tokens #4380
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are "machine key" and "personal access token" interchangeable?
I prefer PAT / "token", but don't have strong feelings either way, especially if the behaviors are the same. The main rationale is I haven't seen "machine key" used commonly in software like this, but 🤷🏼
I find "machine key" a bit confusing as we have machine keys in Tailscale as well. |
machine key is programmer codename 100% - it's because the data model is an api key with the login type "machine". I can change this to whatever makes the most sense for product. In v1 we used |
Tokens makes sense to me! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks fine but you still say "machine token" in a lot of places. Also, using both "api key" and "token" and "key" and "session token" for the same thing is confusing and we should just stick to one where possible IMO
Closes #3692