Level 2 content now opens only for people you authorise
Level 2 exists so we can decrypt your content for people you have approved. It did not work — the key travelled inside the page and access checks refused everyone — so in practice anyone with the link could read it. Access is now granted one person at a time.
Level 2 is for content you want decrypted for particular people without handing every visitor a key. We decrypt at the edge, but only for someone your own system has vouched for.
What was wrong. Workloads built in the portal carried their key inside the page, and the checks that were meant to control access refused every request. The result was the worst of both — nobody could be granted access properly, and anyone holding the link could read the content anyway. Content we had already decrypted could also be reused for later visitors who had no permission at all.
What is true now. No page we serve carries a key. Each viewer is granted permission that lasts a short time and is issued for them alone. Your own server asks for that permission on behalf of someone it has already signed in, so your users never need an account with us, and you can withdraw one person’s access without disturbing anyone else. Every grant and refusal is recorded, so you can see what was opened and who asked.
Was anything of yours exposed? No. There were no Level 2 workloads on the network when this was found.
How to deploy one
- Deploy your site as Level 2.
- In the portal, enable the new access permission on the deploy token you will use. It is off by default, so no token you already have gains it.
- Have your server request access for each signed-in user and pass it to the page.
- The page reads the content for as long as that permission lasts. Your server asks again when it expires, and simply stops asking for anyone you revoke.