Overview
Users of the Kerio Connect server, specifically those with accounts imported from Active Directory, may encounter an issue where they are unable to add app passwords. After generating a password, it appears on the page, but after saving, the list is cleared. This issue does not affect local users created on the server. The problem is often identified when attempting to set up 2FA for a test account, resulting in the error message: 'Failed to configure 2FA, error code: TFAANoSetupError'. The root cause of this problem is an outdated Active Directory Extension for Kerio Connect (KADE) on the AD Server.
Solution
To resolve this issue, you need to update the Active Directory Extension for Kerio Connect (KADE) on the AD Server. Follow the steps below:
- Access the AD Server.
- Locate the Active Directory Extension for Kerio Connect (KADE).
- Check for any available updates and install them.
- After updating, retry adding app passwords on the Kerio Connect server.
Summary
Updating the Active Directory Extension for Kerio Connect (KADE) on the AD Server resolves the issue of being unable to add app passwords for accounts imported from Active Directory on the Kerio Connect server.
FAQ
-
What is the cause of this issue?
The issue is caused by an outdated Active Directory Extension for Kerio Connect (KADE) on the AD Server. -
Who does this issue affect?
This issue affects users of the Kerio Connect server with accounts imported from Active Directory. -
How can I prevent this issue in the future?
Regularly updating the Active Directory Extension for Kerio Connect (KADE) on the AD Server can help prevent this issue.