FW3550 19.0v1 Troubleshooting Multifactor Authentication On Sophos Firewall
FW3550 19.0v1 Troubleshooting Multifactor Authentication On Sophos Firewall
Authentication on Sophos
Firewall
Sophos Firewall
Version: 19.0v1
[Additional Information]
Sophos Firewall
FW3550: Troubleshooting Multifactor Authentication on Sophos Firewall
April 2022
Version: 19.0v1
© 2022 Sophos Limited. All rights reserved. No part of this document may be used or reproduced
in any form or by any means without the prior written consent of Sophos.
Sophos and the Sophos logo are registered trademarks of Sophos Limited. Other names, logos and
marks mentioned in this document may be the trademarks or registered trademarks of Sophos
Limited or their respective owners.
While reasonable care has been taken in the preparation of this document, Sophos makes no
warranties, conditions or representations (whether express or implied) as to its completeness or
accuracy. This document is subject to change at any time without notice.
Sophos Limited is a company registered in England number 2096520, whose registered office is at
The Pentagon, Abingdon Science Park, Abingdon, Oxfordshire, OX14 3YP.
DURATION
3 minutes
In this chapter you will learn how to resolve problems when a user is unable to login using a token
for multi-factor authentication.
There are different types of one-time password. You can use either software tokens, such as the
Sophos Authenticator App or Sophos Intercept X App that are available for Android and iOS, or
hardware tokens, if they conform to RFC 6238.
Authentication problems with one-time passwords are almost always caused by a time difference
between the Sophos Firewall and the device with the token, usually a mobile phone.
In /log/access_server.log you will see that the OTP token is rejected because it is a bad code, or the
token is not active.
First check that the token is enabled, and if it is not, enable it.
=/
If the token is enabled and you are seeing this error, compare the time on Sophos Firewall with the
device the token is being generated on for the user.
2 3
It may not always be possible to correct the time on the token. In this case the firewall can
compensate for the time difference.
As a temporary workaround you can also add additional one-time codes to the token. These can be
given to the user so that they can login even if their token is not working or they have lost it.
These codes should be communicated to the users in a secure manner. It is important to note that
the codes do not expire until they are used or unless an administrator manually removes them.
Authentication problems with one-time passwords are almost always caused by a time
difference between the Sophos Firewall and the device with the token, usually a mobile
phone
OTP time-offset synchronization prompts for entry of the current token code and
Sophos Firewall will show how far out of sync it is
As a temporary workaround you can also add additional one-time codes to the token
Here are the three main things you learned in this chapter.
Authentication problems with one-time passwords are almost always caused by a time difference
between the Sophos Firewall and the device with the token, usually a mobile phone.
OTP time-offset synchronization prompts for entry of the current token code and Sophos Firewall
will show how far out of sync it is.
As a temporary workaround you can also add additional one-time codes to the token.