-
Notifications
You must be signed in to change notification settings - Fork 1
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
release v2023.12.0 + email auth #66
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
| Invitations | 100 | | ||
| Tags | 100 | | ||
| Authenticators per user | 10 | | ||
| API keys per user (long-lived) | 10 | |
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.
is this clear enough? or should we further explain the difference between long-lived and expiring?
@@ -54,6 +54,8 @@ Navigate to your user page by clicking on "User Details" in the user dropdown me | |||
|
|||
Click on "Create API keys" and follow the prompts to add the generated public API key. You'll be required to authenticate with the same authenticator used during onboarding. After this succeeds, you should be all set to interact with our API. | |||
|
|||
NOTE: if you would like to manually your locally stored public/private API key files (e.g. `key.public`, `key.private`), you will have to save the files without newlines (which occupy extra bytes). For example, for VIM, use `:set binary noeol` or `:set binary noendofline` before writing. |
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.
note on usability: this currently only affects api keys created via CLI (api keys created via dashboard app are saved as json files). but this matters if users are trying to manually copy/paste their api key credentials into local files, in which case they'll have to get rid of newline characters.
73b391e
to
3024ad3
Compare
3024ad3
to
300dbf7
Compare
300dbf7
to
ce75e92
Compare
ce75e92
to
964033d
Compare
964033d
to
3f45638
Compare
3f45638
to
9f9f25d
Compare
9f9f25d
to
76d1263
Compare
76d1263
to
cd7ee61
Compare
No description provided.