Create Auth Tokens with PHP
Working with OAuth and similar authentication protocols requires the use of temporary tokens which represent unique handshakes between multiple web services. These tokens must be unique, securely stored, and the longer, the better.
Since I've been out of the PHP game for a while, I was researching how to create such tokens without additional libraries. The following snippet does the trick:
// bin2hex(random_bytes($length)) $token = bin2hex(random_bytes(64)); /* Examples: 39e9289a5b8328ecc4286da11076748716c41ec7fb94839a689f7dac5cdf5ba8bdc9a9acdc95b95245f80a00d58c9575c203ceb541507cce40dd5a96e9399f4a 1c46538c712e9b5bf0fe43d692147004f617b494d004e29daaf33e4528f253db5d911a690856f0b77cfa98103c8231bffff869f179125d17d28e52bfadb9f205 ... */
If you aren't using PHP7 or above, you can fallback to the following:
$token = bin2hex(openssl_random_pseudo_bytes(64));
Having the backing of OpenSSL for token generation gives confidence that the token will be unique. Of course you can also do a storage check to ensure the token isn't already in use, but if you use a length of 64 or larger, the chances you repeat a token are incredibly slim!
Thanks for sharing!
I’ve used this, because it’s produces a shorter string:
Usually I replace
_, so it doesn’t need encoding anywhere:
A word of advice: don’t use
openssl_random_pseudo_bytes()as a fallback for
random_bytes()in PHP 5.x, use the
random_compatlibrary instead: https://github.com/paragonie/random_compat.
Thanks for the trick. How’s the
Sound is great!!!
It can be done either way, and values in a GET request aren’t really any more visible than values in a POST request. If anybody can “see” (i.e. intercept) the request, he can see everything you’re sending. In the end an HTTP request is just a bunch of HTTP headers possibly followed by a body. The URL is send in the first GET /foo/bar HTTP/1.1 line, other values are just send in different, following lines.
So it’s up to you where you expect your authentication token to be send. You can require it to be a query parameter that is appended to every request:
To really use the HTTP protocol as intended though, you should use the Authorization HTTP header:
Authorization: MyScheme 123456:abcde…
The content of this header is entirely up to you. It usually specifies an authorization method like Basic, followed by whatever you want to require for authentication. This can simply be the username and password, a hash of them, an opaque token the client has obtained at some point or anything else really.
I’d recommend a token system or a request signing system, with the latter being very much preferred. In a request signing system, the client has to obtain a token from you. It then sends a hash of this token and certain characteristics of the request to authenticate the request, e.g. sha1(Token + Timestamp + Request URL + Request Body). Your server can validate this without the client having to send the token in plain text on each request.
Following is the code I tried on my own but I don’t know whether it’s right or wrong. Is my approach correct or wrong. Please someone analyse it and let me know your feedback on it.
To create a token i use this function which takes as parameters, the user’s data