Skip to content
Ownkube

Access protection

Access protection puts a login wall in front of a public web app without writing any auth code. Visitors enter a username and password before they reach your app. Turn it on from the deployment’s Security tab.

Turn it on

Section titled “Turn it on”

  1. Open the Security tab

    Go to the deployment’s page in your dashboard and open Security.

  2. Choose Password protection

    Set a username and a password. The password is visible to members of your organization so you can share it with the people who need it.

  3. Save

    Ownkube updates the app’s routing and rolls the change out. Once it is live, every visitor sees a browser login prompt before any request reaches your app.

Password protection uses HTTP basic authentication, so it works in every browser and with curl -u user:password. Change the password from the same tab at any time; turn the toggle off to make the app public again.

Where it applies

Section titled “Where it applies”
  • Starter clusters only. Not on Ownkube Compute, and not on Production (EKS) clusters.
  • Public web apps only. Workers, jobs, databases and caches have no public URL to protect.
  • Cluster platform 0.14.1 or newer. If the tab is greyed out with a version note, apply the pending platform update first.
  • Every hostname. The wall covers the ownkube.app address and any custom domain linked to the app.

Good for

Section titled “Good for”

Staging environments, internal tools, and gating a site before launch: anywhere you want a public URL to exist without being open to everyone yet. For anything that needs per-user accounts, put real authentication in your app and leave access protection off.

Custom domains Serve a protected app from a hostname you own.
Public hostnames How an app gets its public address and certificate.
Environments Keep a staging copy of your app behind the wall and promote when ready.