Skip to content
This repository has been archived by the owner on Nov 27, 2018. It is now read-only.

Initially cache user login info? #27

Open
ah0lland opened this issue Jun 19, 2017 · 1 comment
Open

Initially cache user login info? #27

ah0lland opened this issue Jun 19, 2017 · 1 comment

Comments

@ah0lland
Copy link

I initially attempted to download and configure this credential provider (http://download.multiotp.net/credential-provider/). As part of the installation it asks for your username, password, and pin, and then creates a .db file for the user which is presumably the credentials cache. I was unable to get that provider working, so I chose to uninstall.

After installing this provider, I followed the client/server instructions and attempted to authenticate but failed. I looked at the log and it shows:

2017-06-19 20:03:06 warning System Error: database file C:\multiOTP\users\REDACTEDUSER.db for user does not exist

I placed the REDACTEDUSER.db that was initially created by the first credential provider I tried (http://download.multiotp.net/credential-provider/) in a users folder in the multiotp directory. Once the user db that was created by the other program is restored to the multiotp directory I am able to successfully authenticate. I don't see any commands or options to cache a users credentials using this credential provider. Is there anyway to request the user cache from the server, or do I need to create a script that syncs users from AD on every computer?

I am running multiotp version 5.0.4.7 multionetimepassword-credential provider version 3.0.701.1530 and windows 7 enterprise

@multiOTP
Copy link

multiOTP commented Mar 13, 2018

Hello ah0lland, this is a Credential Provider, you should install first a multiOTP server (open source or commercial edition), and you have to create users on this server (and you can sync them directly from AD or LDAP). When the multiOTP server is installed with some users, now you can install the Credential Provider, which will test if the user exists on the server and if the server is working.

Please note that we have enhanced this MultiOneTimePassword-CredentialProvider thanks to various contributors, and it's now available in the multiOTP project (https://github.com/multiOTP/multiOTPCredentialProvider). We will do enhancements in this fork.

Regards,

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants