We've improved how Vercel Authentication handles rewrites between protected deployments. If you have access to the deployment and it belongs to the same team as the original deployment, we now automatically grant access to the rewritten deployment.

Previously, when rewriting to a protected deployment, Vercel Authentication would redirect through vercel.com to authenticate the user, causing the rewrite to become a redirect.

Automatic access between protected rewrites is only applicable if you are already authenticated with Vercel on the original deployment. This new behavior does not apply to rewrites when you authenticate using Shareable Links, Protection Bypass for Automation, or Password Protection.

Read more about Deployment Protection in our docs.