Hello,
If you want to authenticate local users with OpenOTP, the easiest setup is as follows:
During the CP installation, set the "Remote LDAP password check" option to No. The LDAP or local password will still be validated using Windows authentication mechanisms.
For OpenOTP to authenticate a user, the username provided must be found. You have two options:
Create an alias on an existing LDAP account by configuring the local username on an attribute defined in the uid_attrs setting of the /opt/webadm/conf/webadm.conf configuration file.
Create an LDAP MountPoint using the RCDevs Directory, then create the local account(s) inside the RCDevs Directory. After that, you need to create a new WebADM domain for this LDAP MountPoint. For example, name it LOCAL and configured it to target the user search base of the LDAP MountPoint. Remove the "." Domain Name Alias from your other WebADM Domain. There is another setting which must be configured during the CP installation which is the Local alias setting. This setting is the domain value that is going to be sent to OpenOTP when authenticating with local accounts. This allows WebADM/OpenOTP to find local users in the RCDevs Directory. Create a Client Policy for your Windows machine which allow the 2 domains in the Allowed Domain setting. Then try to login with ".\local_account" on Windows, and it should target your LOCAL domain and authenticate the local account with RCDevs Directory. Of course a Token must be registered on the user account...