Closed muqiuq closed 3 years ago
Duplicate of #42
Workaround: install with server address "/" and any secret. After installation, remove the server address and secret from the config.
I am also wondering when the normal installation will be returned. Your Issue is well written. Let's wait for the developers' response ...
localhost
Seems to work too...
Hello, we published a new version where the multiOTP server and secret key is not mandatory anymore. Can you please try it ? Best regards
Good day @multiOTP ! Thanks! This works!
Tested on Windows 11 Enterprise multi-session (outside of Azure). Do not ask me here, aboui ISOs...
Unlike the previous version, the OTP entry screen now writes user@PC-NAME
, which is much clearer than user@WORKGROUP
.
For local authentification only without server the URL of the multiOTP server had to be left empty. This is now no longer possible.
Some more detailed instructions would be very helpful. Also the information if the saved SECRETS are lost or kept.
See: https://github.com/multiOTP/multiOTPCredentialProvider/commit/dfe7333df3896f367db3262a6acf518be173101a#r55465830