An OpenID authentication error when logging into 1C (including from a thin client for a sole proprietor / ИП) most often means that an incorrect username or password was entered when logging into the database. First of all, check that the credentials are entered correctly, rule out typos, an accidentally enabled Caps Lock, and the wrong keyboard layout. If the data is correct but the error persists, contact the database administrator or the person responsible for 1C — the password may have been changed or the account may have been locked.
Why the OpenID authentication error appears
OpenID is the mechanism in 1C responsible for verifying the identity of a user when logging into an information base. When the system reports an OpenID authentication error, it has essentially failed to confirm that you are the user you claim to be. The most common and simplest cause is an incorrectly entered username or password. This is especially relevant for the thin client, where login is performed through a separate window and the database connection settings may have been saved incorrectly.
What to do first
Check that the login data — the username and password — is entered correctly. Make sure that:
- there are no typos (including extra spaces before or after);
- the Caps Lock key is not accidentally enabled — the password is case-sensitive;
- the correct keyboard layout is used (Cyrillic/Latin);
- you are entering exactly the username and password that were set for this user in the database.
After entering the username and password correctly, logging into the database should proceed without an OpenID authentication error.
Step-by-step verification procedure
- Close the login window and open it again — sometimes the login field retains the value from the previous user.
- Enter the username manually, without relying on autocomplete or saved values.
- Type the password in a separate text field (for example, in Notepad), make sure it looks correct, and then copy or retype it without any extra characters.
- Check the Caps Lock indicator and the current keyboard layout in the system tray.
- Try logging in again. If the error is gone, the cause was indeed a typo or the case of the characters.
If the data is entered correctly but the error remains
When you are sure the username and password are correct, but the system still returns an OpenID authentication error, the cause may lie with the database or its settings rather than with the input. In this case:
- check the current credentials with the database administrator or the person responsible for 1C in your company — the password may have been changed;
- check whether your user account has been locked (for example, after several failed login attempts or by the administrator's decision);
- check whether the database connection address has changed, if you work through a web client or a thin client over the network;
- make sure you are logging into the correct database and not into its copy or a test instance, where the credentials may differ.
For a sole proprietor (ИП) who works in the database alone, the situation is usually simpler: the entrepreneur is effectively the administrator. In this case, recall whether you changed the password during the latest settings adjustments, and check whether the current connection data is saved in the list of information bases.
Thin client specifics
When working through a thin client, login is performed remotely, so connection nuances are added to the typical causes:
- the base list may contain an outdated or incorrect address — check the settings of the specific information base;
- if the database is published on a server, login depends on the availability of that server and the correctness of its settings;
- sometimes it helps to delete the saved login parameters and enter the username and password again manually.
If the problem recurs for several users at the same time, this indirectly indicates that the issue is not with a specific password but with the database or server settings — in that case the solution clearly lies with the administrator.
Common mistakes
- An extra space at the beginning or end of the username/password, especially when copying from an email or messenger.
- An enabled Caps Lock — the password is entered with the correct letters but in a different case.
- The wrong layout: the password is typed in Latin instead of Cyrillic or vice versa.
- An attempt to log into someone else's or an outdated database with the "correct" password from another database.
- Using an old password after the administrator has changed it.
- Multiple failed login attempts, due to which the account may have been temporarily locked.
What to check
- The correctness of the username and password: typos, extra spaces, case, layout.
- The state of the Caps Lock key and the current input language.
- That login is performed into the correct information base, not into a copy or a test.
- The currency of the credentials with the database administrator or the person responsible for 1C.
- Whether the user account is locked.
- For the thin client — the correctness of the database connection address and settings.
In most cases, the OpenID authentication error is resolved by simply re-checking the username and password. But if the input is definitely correct, further actions are up to the database administrator, who will restore or reset the password and unlock the account.