When creating a user in Kerio Connect, the user can either be created locally or by mapping the user from Active Directory (AD). The authentication mechanism for that user will accordingly be using the Kerio Connect database or the AD. This article explains why the same user cannot have different authentication methods in Kerio Connect.
- If a user is created as a local user, then, the credentials used for logging in are stored in the Kerio Connect database for later reference when the user logs in to Kerio Connect.
- If a user is created by mapping it from the AD, then, the credentials used for logging in will be the same as the user's AD credentials.
- Since it is the same user in the Kerio Connect server, the authentication mechanism for this user in Kerio Connect will always be what it was when the user was created. It cannot be one when adding the user in Kerio Connect and the other when the user is logging into Kerio Connect.
- If the authentication mechanism for a user needs to be changed, then, it is recommended to create a new user as per your requirement.
- If this doesn't suffice, then, you can submit a feature request on our forums for it.