মূল কনটেন্টে যান
Localtonet Localtonet ড্যাশবোর্ড

এই পেজ এখনো বাংলা ভাষায় নেই। ইংরেজিতে দেখানো হচ্ছে।

Single Sign-On with a username and password

Needs Balance HTTP tunnels

এই পাতার সহায়তা
এই পেজে 7 সেকশন
  1. When to use it
  2. Before you start
  3. Steps
  4. Add the provider and its users
  5. Turn it on for a tunnel
  6. Test it
  7. Manage users
  8. How it differs from Basic Authentication
  9. Troubleshooting
  10. Related pages

The Username-Password provider is built into Localtonet. You define the users yourself, and visitors type their username and password on Localtonet's sign-in page before they can open an HTTP tunnel. No external identity provider is involved.

When to use it #

  • The people who need access have no common Google, GitHub, Microsoft or GitLab account, or you do not want to register an application at one of those providers.
  • You want to give several people their own username and password, and reuse the same set of users on more than one tunnel.
  • You want to offer a password next to an external provider. Both appear on the same sign-in page.

Before you start #

Steps #

  1. Add the provider and its users #

    Open My Tunnels › HTTP and select SSO at the top of the page. In the SSO providers dialog, select Add provider.

    FieldValue
    Provider nameAny name, for example Staging users. You see it in the tunnel settings.
    Provider typeUsername-Password
    ActiveOn

    When you choose this type, App credentials, Endpoints & callback and Email access rules disappear and Sign-in users appears. Enter a Username and a Password in the first row. Select Add user for each further person. At least one user is required.

    Select Save provider.

  2. Turn it on for a tunnel #

    Under Your tunnels, select Settings on the tunnel, then Manage next to SSO Providers. In the Single sign-on dialog, turn on Require sign-in and the switch of your provider. Select Save.

    The same dialog has a Usernames list under Who can sign in. The lists and the Sign-in paths are explained in the overview.

  3. Test it #

    Open the tunnel URL in a private browser window. Localtonet shows Sign in to continue with a username and password form. After you sign in, you are sent back to the tunnel and your service loads. A wrong entry shows "Invalid username or password."

Manage users #

Open the SSO providers dialog, select Configure on the provider, make the change and select Save provider. Nothing changes until you save.

TaskHow
Add a userSelect Add user and enter a username and a password.
Change a passwordType the new password in the row of that user.
Keep a passwordLeave the password field of a saved user blank.
Rename a userChange the username and enter a password. A renamed user needs a password, like a new one.
Remove a userSelect Remove user (the cross at the end of the row).

Saved passwords are never shown again, not even to you. If someone forgets theirs, set a new one.

Each username must be unique within the provider. Do not create two usernames that differ only in upper and lower case: they count as the same user at sign-in.

One provider, many tunnels. A provider is available to all your HTTP tunnels. When you change a password or remove a user, it applies to every tunnel that uses the provider.

How it differs from Basic Authentication #

A tunnel also has a simpler setting called Basic Authentication, described in Access control. Both ask for a username and a password, but they work differently.

Username-Password provider (SSO)Basic Authentication
Where the visitor signs inOn Localtonet's sign-in page, Sign in to continue.In a sign-in prompt of the browser.
UsersAs many users as you add to the provider.One username and password for the tunnel.
Where it is setOnce as a provider, then turned on for each tunnel.In the settings of each tunnel.
Other sign-in methodsCan be offered next to Google, GitHub and other providers.None.
Protect only some pathsYes, with Sign-in paths.No.
Sign outYes, with a Sign-out path.No sign-out link.
Scripts and API clientsCannot pass. They are redirected to the sign-in page.Can send the username and password with each request.
Tunnel typesHTTP.HTTP, File Server and MCP Gateway.
BalanceRequired.Not required.

Troubleshooting #

"Add at least one sign-in user with a username and password."

A Username-Password provider cannot be saved without a user. Fill in the first row.

"Enter a password for each new or renamed user."

A row has a username but no password, and it is not an unchanged saved user. Enter a password in that row.

"Enter a username for each password."

A row has a password but no username. Enter the username or remove the row.

"Each username must be unique."

Two rows have the same username. Change or remove one of them.

"Invalid username or password." on the sign-in page

Check the spelling of the username in the provider. If the password is in doubt, set a new one and select Save provider. Also make sure that you saved the provider after adding the user.

There is no username and password form on the sign-in page

The provider is not turned on for this tunnel, or it is set to inactive. Check both.

"403 - Access Denied" after signing in

The username and password were right, but a rule on the tunnel refused the user. Check the lists under Who can sign in. After you correct a rule, wait a minute and reload.

সাপোর্ট