Troubleshooting sign-in
This page lists what people see when signing in to Merge Pilot, or linking an account, goes wrong: the exact message, why Merge Pilot shows it, and what to do. How sign-in works is described in Sign-in.
Look first: the company's audit log. Refused sign-ins are written with status Failure and the reason: login (password or directory), ldap_login (directory groups), oauth_callback (GitLab or GitHub), sso_login (identity provider) and session_refused (a session that could not be renewed). A failed sign-in with a user name no account has goes to the platform's log.
On the sign-in page
"invalid username or password"
Why: the user name and password matched no Merge Pilot account, and, when a company was chosen, its company directory (LDAP) did not accept them either. The directory is only asked when it is turned on for the company and on the platform, and only when the person chose the company first (by their work email or under Or choose your organization).
What to do:
- Directory users: start from the work email or the company list, so the page says Use your directory (LDAP) user name and password. Without a company, only Merge Pilot passwords are checked.
- Each wrong attempt counts towards the lockout below.
A directory that cannot answer gives the next message instead, never this one.
"the company directory cannot be reached: try again later or ask your administrator"
Why: the company directory (LDAP) could not say whether the password is right: it could not be reached, the secure (TLS) connection to it failed, it refused Merge Pilot's bind user, or its search failed. The password was not checked. This does not count towards the lockout. Written as ldap_login with status Failure and the reason.
What to do: try again later. Administrators: check the directory with Test connection on the company's directory card (see Company directory (LDAP)); the audit entry says which part failed.
"too many failed sign-ins: this user name is locked for 15 minutes from your address, try again in N minutes"
Why: 10 failed sign-ins (or fewer under the company's password policy) for this user name from this address within 15 minutes. That address is locked out of that account for 15 minutes (or the company's lockout, which the message names); other addresses are not affected. The message says how many minutes are left. Written as login_locked.
A locked account is refused even with the right password. Directory accounts are counted under the account's own name, so typing another form of it (user name or account name) counts towards the same lockout. The policy is the account's: naming another company on the sign-in page does not loosen it.
What to do: wait the minutes the message gives. Nothing in Merge Pilot lifts the lockout earlier: setting a temporary password does not end it. See Failed sign-ins.
"too many failed sign-ins for this account, try again in a few seconds"
Why: 5 or more failed sign-ins of this user name within 15 minutes, from any addresses. Each further attempt must wait, from 1 second doubling up to 30 seconds. The account is never locked by this.
What to do: wait a few seconds and try once, carefully. If someone else is guessing the password, change it.
"rate limit exceeded, please try again later"
Why: too many sign-in attempts from this client address within a minute (30 a minute by default, for the whole installation). People behind one shared address (a proxy or a NAT gateway) share this limit.
What to do: wait a minute and try again.
"user account is deactivated"
Why: an administrator deactivated the account, or its company is inactive.
What to do: ask a company admin to reactivate the account on the Users page, or a platform admin to reactivate the company (see Deactivating a company).
"signing in with a Merge Pilot password is turned off for your company"
Why: the password was right, but Merge Pilot passwords is off on the company's Sign-in tab or on the platform.
What to do: sign in the way the company offers (directory, identity provider, GitLab or GitHub), or ask an administrator to turn passwords on (see Two levels: platform and company). Platform admins always sign in with their password.
Merge Pilot passwords are turned off. Sign in with your work email.
Why: the email typed belongs to no company's Email domains of this company, and the platform turned Merge Pilot passwords off, so there is nothing to sign in with.
What to do: type the work email whose domain the company registered, or choose the company under Or choose your organization. A company admin adds the domain on the company's Sign-in tab (see Finding this company on the sign-in page).
<company> has no way to sign in turned on. Ask an administrator.
Why: the company has every sign-in method off, or only methods the platform turned off.
What to do: a company admin turns a method on in the company's Sign-in tab, or a platform admin turns it back on under Settings → Sign-in. Platform admins can still sign in with Administrator? Sign in with a Merge Pilot account.
The company is not in the list
Why: a company is listed under Or choose your organization only when it is active, Show this company in the sign-in page's company list is on, and it offers more than Merge Pilot passwords.
What to do: type the work email instead, or have a company admin set the company's email domains or turn the listing on (see Finding this company on the sign-in page).
The page asks for a new password
Why: an administrator set a temporary password. Until it is replaced, Set a new password is the only page the account can use.
What to do: choose a new password (Save and continue). See Passwords.
Saving sign-in settings: "you would no longer be able to sign in: …"
Why: a change on the company's Sign-in tab or to its company directory would leave you without any way to sign in (password, directory, identity provider or linked GitLab or GitHub account). When it would lock out others instead, Merge Pilot names them and asks Save a sign-in change that locks people out?.
What to do: link an identity provider or VCS account in My profile first, or keep your way of signing in on. For the others, invite them to link an identity provider on the Users page before saving, or confirm with Save anyway (see Changes that would lock people out).
Company directory (LDAP)
"your directory account is not in a group that may sign in to this company: ask an administrator"
Why: the directory accepted the password, but the person is not a direct member of any group in the directory's Only these groups. Groups are read from memberOf, direct memberships only; a nested group does not count. Written as ldap_login with the person's groups.
What to do: add the person to an allowed group in the directory, or add their group to the list (see Groups). This refusal does not count towards the lockout.
"your directory account cannot be added: … is already used by another Merge Pilot account of this company; ask an administrator"
Why: at the first directory sign-in Merge Pilot creates an account, and another account of the company already has that user name or email.
What to do: an administrator renames or changes the email of the other account, or deactivates it if it is the same person's old account (see The account).
Test connection: "the directory could not be reached or refused the bind user: …"
Why: Merge Pilot could not connect to the directory, or the bind user and password were refused. The reason follows the message.
What to do: check the server address, port, connection security and CA certificate, and the bind user. When you change the server, port, bind user, connection security or CA certificate, type the bind password again: the saved one is never sent to a changed connection (see The saved bind password). The test does not check the user filter; sign in with a test person for that.
After GitLab, GitHub or an identity provider
These messages are shown when the person comes back from GitLab, GitHub or the company's identity provider. <provider> is GitLab, GitHub or the provider's name.
| Message | Why | What to do |
|---|---|---|
| No Merge Pilot account has linked this account at <provider>. Sign in another way, then link <provider> in My profile; or ask an administrator for an account. | The company lets in only accounts that exist here (Only accounts that exist here, or an identity provider's New people set to linked people only), and no account of the company linked this outside account. Accounts are never matched by user name or email | Sign in with the existing account (password, directory or another provider), then link the account in My profile (below). Or ask an admin to let new people in (see Signing in with GitLab or GitHub, Who gets an account) |
| This company does not let people sign in with <provider>. Sign in with your user name and password, or your directory (LDAP) account. | The method is off for the company or the platform, or the company's Signing in with GitLab or GitHub is Off | Sign in another way. People can still link GitLab or GitHub in My profile when sign-in with it is off |
| Only accounts with this company's email domains may sign in with <provider>. Use your work account, or ask an administrator. | A new account would be created, and the email the provider gave is not in the allowed email domains | Sign in at the provider with the work account. An account that already linked signs in whatever its email |
| Your account at <provider> is not in a group that may sign in to this company. Ask an administrator. | The identity provider did not send any group of its Only these groups | Add the person to an allowed group at the provider, or change the list (see Identity providers) |
| Another account of this company already has the email from <provider>. Sign in with that account, then link <provider> in My profile. | A new account would be created, but its email belongs to an existing account. Accounts are never merged by email | Sign in with the existing account and link the provider in My profile |
| This account at <provider> is already linked to another Merge Pilot user. | One outside account belongs to one Merge Pilot account | Sign in as the account it is linked to. If that is the wrong person, they unlink it, or an administrator deactivates that account |
| Your account is deactivated. Ask an administrator to re-enable it. | The account or its company is inactive | Reactivate the account on the Users page, or the company |
| Sign-in with <provider> is not set up for this company. Ask an administrator. | The connection's sign-in switch is off, or its OAuth client ID or secret is missing (the company's Sign-in tab then shows Turned on, but no OAuth client is set), or the identity provider no longer exists | Complete the connection's sign-in settings (GitLab, GitHub) |
| This sign-in attempt expired or was already used. Start again. | The sign-in was started too long ago, finished in another browser, or the page was reloaded after it finished | Start again from the sign-in page |
| The sign-in with <provider> was cancelled. | The person declined at the provider | Start again and accept |
| The sign-in link is incomplete. Start again from the sign-in page. | The provider came back without the answer Merge Pilot needs | Start again. If it repeats, check the redirect URI registered at the provider (see the connection's or provider's page) |
| The sign-in with <provider> could not be completed. Try again in a moment. | The provider could not be reached or refused the exchange | Try again. If it repeats, check the client secret saved on the connection or provider |
| Sign-in failed because of a server problem. Try again, or contact an administrator. | Merge Pilot could not complete the sign-in | Try again; if it repeats, tell the platform's operator |
Signed in with the wrong GitLab or GitHub account
- GitHub shows its account picker at every sign-in and every link, so choose the account linked here.
- GitLab uses the account signed in to GitLab in that browser. To use another, sign out of GitLab first, then start again.
Linking an account in My profile
People need a linked GitLab or GitHub account to be assigned change approvals and to vote (see My profile). The Users page marks people without one Not linked.
| What you see | Why | What to do |
|---|---|---|
| <connection>: linking is off. Ask an administrator to turn on the connection's “Enable OAuth” switch. (GitHub: “Sign in with GitHub”) | The connection's sign-in switch is off: Enable OAuth on a GitLab connection, Sign in with GitHub on a GitHub connection. The connection is not offered for linking | A company admin turns it on for the connection and enters the client ID and secret (GitLab, GitHub) |
| <connection>: linking cannot work yet: the connection's … switch is on, but its client ID or client secret is missing. Ask an administrator to complete it. | The switch is on, but the connection has no OAuth client ID or secret (the company's Sign-in tab shows Turned on, but no OAuth client is set). The connection is not offered for linking | A company admin enters the client ID and secret on the connection |
| Could not link <provider> with Linking <provider> must finish in the browser where you started it, while you are signed in. Start again from My profile. | The provider sent the browser back to a browser or tab without your Merge Pilot session, or the session ended meanwhile, or the account still has a temporary password | Sign in, replace a temporary password, then start the link again from My profile in the same browser |
| Could not link <provider> with You are signed in to another company than the one this <provider> sign-in belongs to. Sign in with your account in that company, then link <provider> from My profile. | The signed-in account belongs to another company than the connection or identity provider | Sign in with your account of the connection's company and link from its My profile |
| Could not link <provider> with A platform admin account belongs to no company, so it cannot link <provider>: linked accounts are for people of a company. … | A platform admin belongs to no company, and linked accounts belong to people of a company | Link from your account in the company |
| Could not link <provider> with Your account is deactivated. Ask an administrator to re-enable it. | The account was deactivated while linking | Ask an administrator to reactivate it |
| Could not link <provider> with This account at <provider> is already linked to another Merge Pilot user. | That GitLab or GitHub account is already linked to someone else of the company | The other account unlinks it, or an administrator deactivates it if it is an old account of the same person |
| Could not confirm the <provider> link (Nothing was linked: this page did not start that link, or it was started in another tab. Start linking again from this page.) | The browser came back without the proof it started the link (for example in another tab). A link is saved only after My profile confirms it, so nothing was linked | Start again from this page, in the same tab |
| this is your only way to sign in: link another one first (unlinking an identity provider under Single sign-on) | The account has no other way to sign in | Link another way to sign in first (see Unlinking a sign-in method) |
| this provider gives your role: ask an admin to manage your account instead | The identity provider gives the account its role | An administrator manages the account instead |
| this is your only way to sign in: link another one first (unlinking a GitLab or GitHub account) | The account has no other way to sign in | Link another way to sign in first |
| this needs a signed-in session: API tokens cannot change security settings (unlinking) | Unlinking was asked with an API token | Unlink in My profile, signed in |
When a session ends
A session renews itself in the background (see Sessions). When a renewal is refused, the person is sent back to the sign-in page, which says why above the form: You were signed out (…), with one of the reasons below. Dismiss hides it; it also goes away at the next sign-in.
| Reason on the sign-in page | Why | What to do |
|---|---|---|
| your sign-in was withdrawn: sign in again | The directory or identity provider no longer lets the person in (see the audit entries below) | Sign in again; if that is refused, see the directory and provider entries above |
| this way of signing in is turned off for your company | The method the session was started with was turned off | Sign in another way |
| please sign in again | The session could not be checked again the way it was started | Sign in again |
| your account is deactivated: ask an administrator | An administrator deactivated the account, or its company is inactive | Ask a company admin to reactivate it |
| your sessions were ended (by an administrator, a password change or signing out everywhere): sign in again | The account's sessions were ended: an administrator changed its role or company or set a password, the person changed their password, or someone used Sign out everywhere | Sign in again |
| your session expired: sign in again | The session reached JWT refresh token lifetime | Sign in again |
| your session has ended: sign in again | The session no longer exists: signed out, ended by an administrator, or the oldest of more than 20 sessions | Sign in again |
The audit log keeps the reasons that come from the sign-in method:
| Audit entry | Why the session ended | What to do |
|---|---|---|
session_refused, reason this way of signing in is turned off for your company | The method the session was started with was turned off for the company or the platform | Sign in another way |
session_refused, reason your sign-in was withdrawn: sign in again | At renewal, the directory no longer found the person or they left its allowed groups, or the identity provider refused the refresh or sent groups outside Only these groups | Sign in again; if that is refused, see the directory and provider entries above |
session_refused, reason please sign in again | The session could not be checked again this way: the identity provider's Sign in again after (hours) passed, the directory could not be reached, or the provider could not be asked | Sign in again |
| None | The session reached JWT refresh token lifetime (7 days by default), the person was deactivated, their password was changed, someone used Sign out everywhere, their role or company changed, or it was the oldest of more than 20 sessions | Sign in again. A platform admin sets the lifetimes in Platform settings |