Sophos XG Firewall - License activation unavailable (error XG-00151). See KB-000043485 for the latest updates.
Hi there,In an XG 115 with the software 18.5.1 MR-1-Build326 I entered several users under Authentication / User, only the entry that was entered with an older firmware is still able to log in via SSL. All users who are now entered are rejected with AUTH errors, so they cannot log in. I compared all entries, they are identical except for the relevant entries. The simple LOG entries are 'reason = "wrong credentials", but I can log in with the same access data, e.g. via the user portal.In the forum I found the following entries to diagnose errors:Select Option 5 (Device Management) > Option 3 (Advance Shell)Run this command to put the access_server service in debug:• service access_server:debug -d -s nosyncOnce you capture the access_server logs in debug, run the same command to put access_server service in normal running mode. Run this command to check service status :• service -S | grep access_serverSFVUNL_VM01_SFOS 17.5.11 MR-11# service -S | grep access_serveraccess_server RUNNING,DEBUGUsing the command 'tail –f /log/access_server.log I was able to extract the following error:ERROR Oct 22 19:49:30.431855 [access_server]: pg_db_handle_check_crt_fingerprint: row count: 1 value 0 DEBUG Oct 22 19:49:30.431868 [access_server]: pg_db_submit_response: Request Processed: res_type=-1 WARNING Oct 22 19:49:30.431881 [access_server]: (check_crt_fingerprint): wrong fingerprint for user test1 DEBUG Oct 22 19:49:30.431893 [access_server]: (send_pam_response): resp_code =3, clienttype=13, message='Login failed. Wrong fingerprint of certificate.' DEBUG Oct 22 19:49:30.431905 [access_server]: send_pam_response: message:'Login failed. Wrong fingerprint of certificate.', len:47, data:'Login failed. Wrong fingerprint of certificate.'The user 'test' created with a different firmware version can log in with the same certificate without any problems. What has changed with the newer firmware versions that newer user entries can no longer connect or how can I prevent these errors?I am grateful for every tip.regardsGerd Beckmann
Most likely the new users, are using in their password some invalid characters such as #,%, etc.
Try creating a new user with a simple password without special characters, see if that resolves…
This issue most likely generates, because the user is a different user generated by the firewall.
Means: You have two separate authentication setups: User Portal and SSLVPN. If User logins via User Portal using AD Server or Radius, it will generate a config for this user. It could be a different user after all, using VPN after the download. Check its the same authentication method. If not, check if you change this.
Hello, thank you for your answers.
No, I only use local authentication, there are no entries under Authentication / Server. All methods entered under Authentication / Services use the same local authentication.
There is only one functional user who was probably created under a different firmware version; newly created users all receive the error message that the login has failed. All users are in the same group and have exactly the same settings except for different names / passwords / email addresses.
Add: After the user request to log in i found in the sslvpn.log this entry:
Error: cannot open /tmp/openvpn/serverusers.conf to verify user
Maybe that's another clue to the solution?
Try creating a new user with a simple password without special characters, see if that resolves the issue.
Hi, thanks for your reply,
i tried all those combinations before, my last user becomes the name 'test1' and the password 'Test12345' with the same result.
Did you replace a certificate or something?
no, i've only two certificates installed, the default ApplianceCertificate and a 'locally signed' certificate for the SSL -VPN. All the defined SSL-Users uses the same certificate, only one of them can connect.
Does Sophos possibly use a different encryption method for user passwords in newer firmware versions, which may be incompatible with the SSL identification module?
I started an export (Backup & Firmware / Import Export / Export selective configuration) and downloaded the user data. Despite identical passwords, the hash form is different. However, other parameters may also play a role here, so that this approach may be a dead end.
<User transactionid = "">
<Username> test </Username>
<Name> test </Name>
<Password hashform = "mode1"> $ sfos $ 7 $ 0 $ Pp3KDUowtDpzgQJ7b0d ...
<Username> test1 </Username>
<Name> test1 </Name>
<Password hashform = "mode1"> $ sfos $ 7 $ 0 $ lPuAw_BYSpUWDIEvRe ...