TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

API Key Authentication Best Practices

38 pointsby nathantottenover 2 years ago

4 comments

sghosh2over 2 years ago
The checksum validation was something I hadn't come across before. Interesting way to minimize the load on the API key store.
评论 #33819576 未加载
ChaosMuppetover 2 years ago
With regards to secret scanning, a shout-out to the &quot;secret-token&quot; URI scheme <a href="https:&#x2F;&#x2F;datatracker.ietf.org&#x2F;doc&#x2F;html&#x2F;rfc8959" rel="nofollow">https:&#x2F;&#x2F;datatracker.ietf.org&#x2F;doc&#x2F;html&#x2F;rfc8959</a><p>Also, in addition to showing the creation date of the API key, I find it super friendly if it is possible to name the API key (and&#x2F;or add a note to it).
devCreekover 2 years ago
Regarding retrievable vs. irretrievable, I think is a matter of who do you delegate the ownership of the security. Using Irretrievable, you are transferring that to your users, which in a lot of scenarios just store them in plain text in non secure places.<p>I think having the chance to retrieve the api keys gives a much better Developer Experience to your consumers.
评论 #33819993 未加载
molmorgover 2 years ago
Author of the article here - look forward to any discussion here. Curious how many folks have already implemented something like this themselves... did you make different decisions?