Password protection

Password protection asks visitors for a password before they can open a web service. Use it for a staging copy of your app, a site before launch, or anything only a few people should see.

Visitors see an Appentic sign-in page on your app's own address, not the browser's password pop-up. Once they've entered the password, they stay signed in on that address for a week.

Turn it on

1. Open the web service's Settings.
2. Under Access, enter a password of 8 to 128 characters.
3. Click Protect with a password.

It applies within a few seconds, on the service's appentic.app address and on its custom domains.

Change the password

Under Access, enter a new password and click Change password. Everyone signed in with the old password has to sign in again.

Turn it off

Under Access, click Remove password protection and confirm. Anyone can open the service again within a few seconds.

Good to know

• After five wrong passwords within a minute, a visitor has to wait before trying again, and longer each time it happens again.
• It protects the whole service, every page and every request, including your app's API.
• There's no fee. It takes 32 MB of memory on one of your machines, or on one machine per zone if protected services run in several zones.
• A web service in a load balancer can't have a password, and a service with a password can't join one.
• It works alongside a firewall. The password keeps a site private, and the firewall keeps a public site safe.
• To keep a service away from the internet entirely, make it a private service instead.