Authenticated URLs

Authenticated URLs give you more control over access to your content. Token authentication ensures that a URL is only accessible during a defined time. Once a token has expired, it is not possible anymore to access the content, and new URLs must be generated in order to access the secured content again. Using authenticated URLs may be useful if:

  • Your customers upload personal/medical/sensitive data.
  • You don't want your content to be rendered by unauthorized users.
  • You want your content to be accessible only within a specified time frame.
  • etc.
Authenticated URLs work alongside with custom domains, so you need to set up custom CNAME first. The format of an authenticated URL depends on CDN provider the custom domain has connected to. Currently, we're working with  Akamai and  KeyCDN.
This is how secure URL will look like:
  • For Akamai
https://cdn.yourdomain.com/{uuid}/?token=exp={timestamp}~data=my_signature_data~hmac={token}
	
  • For KeyCDN
https://cdn.yourdomain.com/{uuid}/?token={token}&expire={timestamp}
	
The timestamp has to be defined as  Unix time.
To generate tokens you would need to set up your backend. There are some ready solutions for most popular languages:
  • For Akamai (C, C#, Erlang, Go, Java, Perl, PHP, Python, Ruby)
Please, contact us if you want to enable authenticated URLs for your project(s).