multiOTP credential provider doesn't work anymore

[dominikjas]

Hello,

we are using the credential provider in a windows domain enviroment. The server and client is updated to the latest version and we have uninstalled all antivirus software. When we try to login we are getting this serror: The serverlog is okay:

• Server version: 5.9.5.5 / VM-006
• Client version: 5.9.5.6

[Viach47]

Hello, It looks like a case, I’v opened last week. https://github.com/multiOTP/multiOTPCredentialProvider/issues/88 Could you check your server log (C:\MultiOTP\windows\log\multiotp.log) have it any records about “bad” login attempts? And at “bad” user PC in multiOTP/config folder, you should be able to enable debug and log in multiotp.ini file. Search and change the following entries: • debug=1 • log=1 Will it create log or not ?

[dominikjas]

Hello, we are using the multiOTP Linux Image, which does not have any possibility to login and gettting a shell. Is there any other possibility to enable this debug log? I installed the Credential Provider on a windows server vm for testing. The problem is the same on this device. I think the problem appears on every device where the caching-file is missing because a new user tries to login. This is the error log:

========================================
multiotp 5.9.5.6
Your script is running from C:\Program Files (x86)\multiOTP\.\
2023-04-24 10:32:40 warning     System  Error: database file C:\Program Files (x86)\multiOTP\.\users\administrator.db for user Administrator does not exist 0   DB03
2023-04-24 10:32:45 warning     System  Error: database file C:\Program Files (x86)\multiOTP\.\users\administrator.db for user administrator does not exist 0   DB03
2023-04-24 10:32:55 debug       Client-Server   Warning: timeout after 5 seconds for ssl://192.168.68.231:443 with a result code of 0 ().   0   DB03
2023-04-24 10:32:55 debug       Client-Server   Info: temporary adding https://192.168.68.231 to the list of banned servers, content not recognized (...)   0   DB03
2023-04-24 10:32:55 warning     System  Error: database file C:\Program Files (x86)\multiOTP\.\users\administrator.db for user administrator does not exist 0   DB03
2023-04-24 10:32:55 warning administrator   User    Error: User administrator doesn't exist 0   DB03
2023-04-24 10:32:55 debug       Debug   Debug: *21 ERROR: User doesn't exist    0   DB03
2023-04-24 10:32:55 debug       Debug   Debug: *Attributes sent to the RADIUS server: Reply-Message := "ERROR: User doesn't exist"  0   DB03

Looks like the server doesn't send the correct answer back.

[dominikjas]

Hello again, I was able to get access to the linux system (ssh port 22422) by adding our publickey via livelinux. I noticed that the Debian was an old debian jessie (version 8) and I thought this would get updated when I am installing the firmware updates. Apparently that's not the case and you have to install the updates manually, which is kinda weird because by default you do not have access to the server. After we adjusted the config, we didn't get any server log either and then decided to download the latest image (with debain 11) and import the config again. The login is now possible, but now the license can no longer be imported, although it does not report an error. The debug log works here now, but after installing the license, no log entry appears here. Out customer is now unable to login and we hope someone can help us soon :-/

[multiOTP]

Hello Dominik, As you have contacted us directly for the commercial version of multiOTP server, we have unlinked the licence in order to allow a new installation of the server. Regards,