Troubleshooting - inWebo Windows Logon

If the installation seems to be fine, but the credential provider is not visible, please check the windows version.

If the version is Windows10 21H1, please be aware that this specific Windows version does not include by default the Microsoft Visual Studio C++ redistributable component. This component is required

See inWebo Windows Logon > Prerequisites

If the push notifications are sent but not received on the trusted device:

• check that the inWebo user login matches the Windows user login,

• check that the ConnectorAlias and AES key values in the appsetting.json file are correct

• check that the trusted device receives inWebo notifications. You can try to send a push notification from a demo page.

If the problem persists, you may try to delete the <user>.dat file.

• Go to the inWebo Windows Logon installation directory (the default one is C:\Program Files\inWebo\WindowsLogon).

• Delete the <user>.dat file

The user should now be able to receive the push notifications.

The <user>.dat file is created after the user logs in for the first time with inWebo Windows Logon. If you see a <user>.dat file when the user has not yet performed a first connection, this may be related to a previous version and you can delete it.

If the user enters the Windows password and the session opens without inWebo MFA, this may be related to the type of Windows account.

The user should have a local or domain account in order to log in. See inWebo Windows Logon > Prerequisites

Microsoft accounts are not supported.

To find out if a Windows Account is a Microsoft account:

1. Go to Start > Settings > Accounts  > Your info (in some versions, it may be under Email & accounts instead).

2. If you see “Sign in with a local account instead”, this means the current Windows account is a Microsoft account.

If you see a green line around the installation window of the inWebo credential provider, this may be related to the antivirus. The antivirus has put the install program in quarantine.

Please refer to your administrator.

After entering the PIN in Authenticator application, a message Unexpected Error appears. This may be related to a duplicate entry of the workstation in the data base. You should check if the workstation is already active in another inWebo Windows Logon connector.

If the workstation is already active in another inWebo Windows Logon connector, delete it from the connector list.

See inWebo Windows Logon > Managing workstations

Start “Services”. The service inWeboWindowsLogon should be present, running, and set up to start automatically.

See C:\Windows\System32 → the IWLCredentialProvider.dll should be present.

The default installation directory is C:\ProgramFiles\InWebo\WindowsLogon

It should contain the following files:

• AuthenticatorService.exe

• appsettings.json

• (after the first connection) <user>.dat

Open the appsettings.json file with a text editor and with administrator rights.

After modifying the appsettings file, you have to restart the workstation.

The registry should contain the following keys:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\Credential Providers\{E21429AB-5836-4410-BF7B-6E2769C094CC}]
@="IWLCredentialProvider"

[HKEY_CLASSES_ROOT\CLSID\{E21429AB-5836-4410-BF7B-6E2769C094CC}]
@="IWLCredentialProvider"

[HKEY_CLASSES_ROOT\CLSID\{E21429AB-5836-4410-BF7B-6E2769C094CC}\InprocServer32]
@="IWLCredentialProvider.dll"
"ThreadingModel"="Apartment"

The user should have a local or domain account in order to log in.

Microsoft accounts are not supported.

To find out if a Windows Account is a Microsoft account:

1. Go to Start > Settings > Accounts  > Your info (in some versions, it may be under Email & accounts instead).

2. If you see Sign in with a local account instead, this means the current Windows account is a Microsoft account.

In case of a Microsoft account, inWebo MFA is not applied. The behavior is the following: the user enters the Windows password and then the session opens.

The last version of the inWebo credential provider is available here: Resources downloads.

To see the version number of the inWebo credential provider that is deployed on a workstation:

1. Go to Windows > Settings > Apps

2. Click on Installed apps

3. Search for “inWebo Windows Logon”

The version is displayed under application name.

1. Open an admin session and the Event viewer.

   

2. In the Event Viewer, go to Windows logs > Application.

   

   Note that the loading of the logs can be slow.

3. There are several log categories:

   1. The known errors that are handled by the service: they appear under the service name InWeboService. We can find for example the exchange between the workstation and the inWebo backend, for each connection.

   2. The errors that are not known appear after the above. They are labeled .NET Runtime and Application Error.

   

To access the logs about connectors:

1. Log on to the administration console v2

2. Go to Audit

3. The inWebo Windows Logon connectors are included in the “SERVICE_MANAGEMENT” category.
   Note that you can filter the logs by category.

To access the logs about connectors:

1. Log on to the administration console v2

2. Go to Audit

3. The inWebo Windows Logon connectors are included in the “WORKSTATIONS_MANAGEMENT” category.
   Note that you can filter the logs by category.

To access the logs about the workstations linked to Windows Logon:

1. Log on to the administration console v2

2. Go to Windows Logon

3. Go to the connector and click on “Workstations”.

   

   You will get the activated workstations list for this connector.