Cloudflare

How do you correctly places your pages deployment behind access? I have tried a few ways but it always returns odd results

If you add access policy 3 times; one for *.<project>.pages.dev, another for <project>.pages.dev, and another for the alias domain, if you try to access the alias domain, you first get the one time code then are redirected to login to the pages.dev application.

If you assign the same access group to all 3 of the access applications, then it'll let you in but in the audit log you can see that it authenticates you against both the alias domain's access, followed by one of the pages.dev ones

Another note, I wouldn't be too concerned about the redirecting but it does sometimes seem to make Chrome show a phishing warning

If the permissions are different between the main alias and the pages.dev domain, then even if you're "supposed" to have access, you'll get a code and be forwarded to the other login screen which you don't have permission for

I can't tell if this is intended behaviour, if I am doing something strange, or what? I'm kind of tempted to upgrade my account just to get support atm for something which may just be a bug 😄