Signed cookie in CDN
Enable authenticated access to CDN without the need to change URL or headers. This is especially useful for referencing a static web page in an IFRAME.
Scenario. When user signs in to example.com, we would first redirect users to a non-cached page on CDN cdn.com, which would set the signed cookies, before redirecting back to example.com.
On example.com, we have an IFRAME that references a static webpage on cdn.com. The static webpage references other images, JavaScript and CSS on cdn.com. The access to the webpage and other resources are authenticated by the signed cookie.
AWS implementation http://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/private-content-signed-cookies.html
Li Huan Jeow
shared this idea
If you are using Azure CDN from Verizon Premium, you can open a technical support case to have this capability setup for you via the rules engine. Overall you would use the token authentication capabilities in Azure CDN from Verizon Premium to accomplish this – https://docs.microsoft.com/en-us/azure/cdn/cdn-token-auth. With token authentication the signed token is sent by default in the query string for your URL’s. The capability you are looking for is the ability to instead have the token sent as a cookie in the client request to the CDN.
We will look at enabling this capability long term without the need to open a support case.
1 comment
-
Sunny Sharma
commented
under review for more than two years now, any update here on this please?