4 ms·
>> Better still, don't use passwords in your API at all. Passwords are for humans. APIs use keys. > this is merely nomenclature, no? What you are calling a key
by e12e 14y ago
>> Better still, don't use passwords in your API at all. Passwords are for humans. APIs use keys.
> this is merely nomenclature, no? What you are calling a key is really a long, random password
Both passwords and keys are shared secrets. A password is a secret a human remembers, and can prove he/she remembers. A key is something a machine stores and can prove it has.
(Actually, an API key can also be a token, eg: "{ hash: " + hash(key+salt+date(now))+"valid from: " + date(now) + "salt: " + salt + "}" -- that is -- if you know the key, you can verify that that the token is indeed valid from the date claimed (and you could add serial numbers and other stuff as well). Note that the user doesn't need to know the key in this case, the user only needs a copy of the token).
So yes, it is nomenclature, but it matters.
[edit: formatting, typo]