Sign in to the Web App

On this page

Before you begin

  • You need an active technician account. The Web App refuses a sign-in when the account is inactive, is not a technician account, holds neither the named nor the concurrent policy, or belongs to a person whose status is inactive.
  • The Web App opens only over a secure (HTTPS) connection. A page requested over plain HTTP is not shown; you get an error page instead.
  • Internet Explorer, and Microsoft Edge in Internet Explorer compatibility mode, are not supported. They are sent to an unsupported-browser page.

In the Web App

Sign in

  1. Open your organization's Web App address. The Sign in page shows a password form, a Sign in with button for each single sign-on provider enabled for the Web App, or both.
  2. Use one of the methods offered:
    • With a password, enter your User Name and Password, optionally select Keep me signed in, and click Sign in.
    • With single sign-on, click Sign in with followed by your provider's name. Over a connection that is not secure, the buttons are disabled with the hint Secure connection required (HTTPS).

If your Web App is configured for Windows authentication, the Web App signs you in with your Windows identity.

If you are already signed in and open the sign-in page, the Web App takes you to its main page, unless a license error is pending.

When the Web App refuses your account or your credentials, the message names your login:

  • For a typed user name and password that fails both the account check and the directory check, the message reads Sign-in failed for user '...'. with your login between the quotes.
  • For Windows authentication, and for single sign-on when an account with your login exists, the message reads Your account '...' is not an active ... account. Please contact your ... administrator. with your login and the product name in place of the dots.

For single sign-on, your Alloy Navigator login must be the value your provider sends for you, apart from letter case (for Microsoft Entra ID and Okta, by default your user principal name). When no account matches, the sign-in is refused, and the message names the product and your user name.

NOTE: After a successful single sign-on, the Web App remembers you on that browser for ten days and signs you in again on your next visit without contacting your provider. If that automatic sign-in fails, the sign-in page shows the error. Signing out clears this.

If you cannot sign in

The refusal message does not tell the causes apart. After a typed user name and password, the cause can be a wrong password or a refused account. An account is refused when it is inactive, is not a technician account, holds neither the named nor the concurrent policy, belongs to a person at the inactive status, or no longer exists: a deleted account gets the same messages as an inactive one.

Other causes show on the sign-in page itself:

  • The Sign in button is disabled: sign-in protection has locked the password form after repeated failed attempts (see Sign-in protection).
  • The Sign in with buttons are disabled with the hint Secure connection required (HTTPS): the page is not open over a secure connection.

When your account uses the concurrent policy, the sign-in is also refused when the limit of concurrent sessions is reached (see User Sessions).

Ask your administrator to check your account. What the administrator does depends on the cause:

  • The account is disabled. The administrator enables it again (see Accounts).
  • Your person record is at the inactive status. You cannot sign in by any method, even when your account is still active. Saving the person record with an active status does not enable the accounts, so the administrator checks them separately. In a new 2026.1 database created with the Default Workflow, the person's status actions described in Persons and Groups change the accounts as well.
  • The account was deleted. A deleted account cannot be restored. The administrator creates a new technician account with the same login in the same form (a DOMAIN\UserName login for Windows authentication, and a password only if the old account had one), gives it the named or concurrent policy, and assigns its security roles again, because role membership is removed with the deleted account (see Create and Maintain Technician Accounts).

Sign-in methods

The Web App supports four authentication methods. Which of them your Web App offers depends on how it is configured.

  • Standard: the user name and password you type are compared with your account.
  • LDAP: a fallback of the password form. If the typed login and password do not match your account, the directory is checked. The directory sign-in is accepted only when your account already exists as a Windows-authentication technician account.
    • A login in DOMAIN\UserName form goes to the directory of that domain.
    • A login without a domain goes to the directory only when exactly one directory is configured and at least one technician account's login begins with that domain name.
  • Windows: the Web App signs you in with the Windows identity the web server has established.
  • Single sign-on (SSO): you sign in with an identity asserted by an external OpenID Connect provider.

If your account is set up for single sign-on and also keeps a password, you can also sign in with its login and password on the password form.

See Authentication Methods and Single Sign-On for how administrators set these up.

Sign-in protection

Your administrator can turn on sign-in protection in the Admin Center's Web App settings (see Authentication Methods). When it is on and the number of failed sign-in attempts within the configured time window reaches the configured maximum, the Sign in button is disabled and further attempts are refused until the lock period ends. A successful sign-in clears the count.

The count is kept per browser session, not per account. Sign-in protection guards the password form only; single sign-on does not use it.

Sign out

  1. In the header, open the profile menu that shows your avatar and name.
  2. Choose Sign Out.

Signing out erases the sign-in information stored in your browser, including what single sign-on saved, ends your session, and returns you to the sign-in page.

NOTE: Sign Out is not shown when your Web App is configured for Windows authentication.

When your session ends automatically

If your session holds a concurrent license, the Web App runs a countdown for it. A session on a named license has no such countdown, and the countdown is off when automatic termination of idle sessions for concurrent users is turned off. When the countdown runs out, the Web App asks the server whether to end the session. If the server answers that it should, a page shows You will be signed out due to inactivity in: with a countdown from 30 seconds.

  • Click Stay Signed In to go back to the page you were on. The page also goes back on its own when your browser reports activity in the Web App.
  • If you do nothing, at zero you are signed out and the Web App shows an error page for the session timeout. Unlike Sign Out, this does not erase the sign-in information stored in your browser.

Administrators set whether idle sessions of concurrent users end, and after how many minutes, on the Admin Center's User Sessions page. They can also end any open session there with Terminate.

Change your password

The Settings page offers a password change unless your Web App is configured for Windows authentication, you signed in through Windows authentication, or your browser holds the provider information that a single sign-on saved there. That is the case after you sign in through single sign-on, and signing out clears it.

  1. In the header, open the profile menu and choose Settings.
  2. In the Password panel, click Change Password.
  3. In the Change Password dialog, your Login is shown read-only. Enter your Old Password, then your New Password and Confirm New Password.
  4. Save the dialog.
    • If the two new values differ, the dialog shows The new password does not match the confirm password. and stays open.
    • If the server returns any other message, the dialog shows it and stays open.
    • Otherwise, the dialog closes and the Settings page shows Password has been changed successfully.