i don’t have an entra id or domain login but would love to try it on my laptop 
Ok internal testing caught some stuff. Can’t fix today but will post an updated beta test later this week.
2 Likes
I am certainly interested in testing 
1 Like
have work laptop with domain login
3 Likes
Beta release. Unsigned. You’ll have to specifically authorize installation;
VivoKey-FIDO-for-Windows-Auth-1.1.1.msi (1.1 MB)
Only Apex supported, for now. Release version will have an option for non-VivoKey authenticators.
4 Likes
Any chance of it being uploaded to the dt/vivokey github ? not that i don’t trust you 
it’s just nice to see what one is running 
First setup took less then 5 minutes and works a treat so far
I have it set up without a pin for now since it did not give me an option for a pin in the fidesmo app.
works great! slower than rohos to login once scanned, but more secure from what i understand
1 Like
sadly not really, and this is because VivoKey is kind of tasked with making money at this point.. it’s really been coasting on DT’s tails since 2018 and basically I need a way to make little inroads into the enterprise markets VivoKey was sort of designed to address. In short, I plan on adding a license key system to allow non-VivoKey authenticators to be used. Have an Apex? Great, it’s free. Want to use a YubiKey, then VivoKey needs a lil scratch for that.
Oh hah.. so yeah a new FIDO authenticator (new yubikey or new applet deployment to Apex) is basically uninitialized and the first time you use it with basically any passkey implementation, you will be challenged by Windows to set a PIN. After that you can use a PIN for enrollment if you want. Good to know that it still works without a PIN though. I hadn’t considered this. I think I will update it to include at least some text to indicate your authenticator has not had a PIN set yet if it encounters this state.
Yeah, should only be a second or two slower. It’s unwrapping the cached password. Rohos just stores your password unencrypted, but VKFFWA wraps the password using your token(s). There should be a security.md file in the installation folder that explains the approach.
5 Likes
Update that makes it clear when an authenticator being enrolled does not have a PIN set.
1 Like
lemme know when you get a chance to test! excited to find out what happens.
1 Like
Probably get to it tomorrow.. been busy with Bear attacks and cleanup last 2 days
3 Likes
haha damn dude.. tell them bears you got testin to do! glad it was your doors/windows and not you.
3 Likes
That’s probably because it’s unsigned and the group policy settings won’t allow it. Can you install other software without a problem (downloaded, not via Microsoft Store)?
1 Like
Never tried, hardly ever use this thing because it’s old and the battery is shot. Been trying for ~3 months to get a replacement from IT, lol.
I was able to set up a test environment with active directory domain. had to make some adjustments to the code but it does work with local machine accounts, microsoft online accounts, and domain accounts. you just need admin credentials or admin permissions on the box to do registration and enrollment. i have not tested yet with entra ID managed online accounts.
4 Likes