Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 3 replies
  • Subscribers 27 subscribers
  • Views 1015 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Sophos Connect 2.0 and SSL Provisioning File

jt86

Identified a bug of somekind here but could use some support/confirmation.

When using the VPN portal with the OTP enabled, the SSL VPN connection needs an OTP even when the provisioning file is set to false for this setting. The first login fails but subsequent logins without the OTP works added to the password. This is really confusing as it doesn't indicate to the users that the OTP is required on first login and the error message is just that of the credentials being invalid.



This thread was automatically locked due to age.
Parents
  • FormerMember
    0 FormerMember

    Hi ,

    Thank you for reaching out to the Community! 

    Thank you for the feedback. 

    I will update you on this after replicating this issue in my LAB and consulting the internal team. 

    Thanks,

  • 0 in reply to FormerMember

    Also one thing to consider using Sophos Connect 2.0 on Windows. I used provisionig file with option to save password and just use 2FA. When user has to change AD password, you can do that by selecting clear credentials. This does not work. I had to first update policy again with new password,exit and start program again. Then it was OK.

Reply
  • 0 in reply to FormerMember

    Also one thing to consider using Sophos Connect 2.0 on Windows. I used provisionig file with option to save password and just use 2FA. When user has to change AD password, you can do that by selecting clear credentials. This does not work. I had to first update policy again with new password,exit and start program again. Then it was OK.

Children
No Data