Yubico Forum
https://forum.yubico.com/

[QUESTION] Desktop Authenticator does not recognize NEO-W8.1
https://forum.yubico.com/viewtopic.php?f=26&t=1466		 Page 1 of 2
Author:  DarkWinter [ Mon Sep 15, 2014 5:33 am ]
Post subject:  [QUESTION] Desktop Authenticator does not recognize NEO-W8.1
I'm having some significant difficulty successfully using the Desktop Authenticator with my NEO in Windows 8.1. I successfully used the NEO Manager to load the YubiOATH applet onto my NEO (it is an older NEO, purchased spring 2013), though I had to "manually" install the YubiOATH applet using the "Install from a .cap file" button. The other two applets (YubiKey TOTP and OpenPGP) installed automatically without my intervention.

I also successfully migrated all my existing OATH secrets from Google Authenticator to Yubico Authenticator. When using my smartphone, everything works flawlessly and it's pretty amazing, if I must say. However, when attempting to use the Desktop Authenticator, I'm seeing some strange and difficult-to-replicate behavior. When I first plugged in my NEO and selected "Show Code", the application prompted me for a password. I did not setup a password for the YubiOATH applet via my smartphone app. Leaving the box blank and clicking "Ok" did not work and presented a box that says "No YubiKey NEO found. Please plugin your YubiKey NEO in one of your USB port".

After some tinkering, I uninstalled the Desktop Authenticator, re-booted my laptop, and re-installed the Desktop Authenticator. I also used my smartphone Yubico Authenticator app to setup a quick, simple password for the NEO. Once I re-installed the Desktop Authenticator, the first attempt to access the NEO worked perfectly with the password. I don't really want a password on my NEO at this time, so I went back to my smartphone, and reset the password this time leaving it blank. Going back to the laptop, the Desktop Authenticator will no longer recognize that a NEO is plugged in, regardless of the USB port I use or how many times I plug it in. I receive the same message as above, with no password prompt.

It may be worth noting that when using the NEO Manager, the first time I plug in my NEO, it appears as HID-only mode. It takes several re-plugs (usually a rapid re-plug) to get it to show up as HID+CCID with touch-eject. It may also be worth noting that I have Slot 2 configured for Windows local logon challenge-response (Slot 1 is YubiOTP). I can't really make heads or tails of the behaviors I'm witnessing and could use some help or clarification.

1) Does use of the Desktop Authenticator require a password to be set on the smartphone Authenticator app?
2) If you leave the password field blank in the smartphone Authenticator app, can you also leave it blank when requested for input by the Desktop Authenticator?
3) How do I get my laptop to consistently recognize my NEO is set as HID+CCID with touch-eject (or -m82 in techie speak, I think)?

Any help appreciated! Thanks!
Author:  Nomadus [ Fri Sep 26, 2014 4:13 pm ]
Post subject:  Re: [Problem] Desktop Authenticator does not recognize NEO -
Hi @DarkWinter; being a year-and-a-half without responses here, did you get your questions/situation sorted out?
Would be curious to know what you found out. Haven't started with NEO myself yet.
Author:  DarkWinter [ Mon Sep 29, 2014 3:51 am ]
Post subject:  Re: [Problem] Desktop Authenticator does not recognize NEO -
No. I only posted this question about two weeks ago, but I've not seen any responses yet. I really like my NEO, I just wish I could get the Desktop Authenticator to work.
Author:  Nomadus [ Mon Sep 29, 2014 4:02 am ]
Post subject:  Re: [QUESTION] Desktop Authenticator does not recognize NEO-
ah, I must have glanced at your user creation date instead of the post date...
ok, so awaiting responses.
sorry about the confusion, unnecessary post.
Author:  Tom [ Tue Sep 30, 2014 7:44 am ]
Post subject:  Re: [QUESTION] Desktop Authenticator does not recognize NEO-
Hello DarkWinter,

I am unable to replicate your issue on Windows 8.1.

Please do the following. Go to the device manager panel and uninstall al USB devices, uninstall the authenticator by removing the folder from /programs/ in windows and reboot.

Unset the password from your android device.

Plug in the NEO on windows should reinstal.

Install the authenticator, right click the icon and SHOW CODES.

----

In case this does not work, you will have to document in details what USB driver you are using, laptop model, security update and latest windows 8.1 update, screenshot of the error, version of the applet, Version of your Yubikey NEO.

Tom
Author:  DarkWinter [ Sun Oct 12, 2014 5:13 am ]
Post subject:  Re: [QUESTION] Desktop Authenticator does not recognize NEO-
I followed the procedures indicated above and they did not work, in fact the Desktop Authenticator does not work at all now. Before, I could get it to work sporadically. Now I only receive the following pop-up message when I select Show Codes.

Quote:
WARNING: No Yubikey NEO detected

Quote:
No Yubikey NEO found. Please plugin your Yubikey NEO in one of your USB port


I am still experiencing the issue (if it is an issue) whereby upon insertion of the NEO, the NEO Manager GUI does not report it in HID+CCID with touch eject mode. I have to re-plug the NEO several times before the NEO Manager GUI shows that the NEO is in HID+CCID with touch eject mode.

My computer is an ASUS N56V with Windows 8.1 Update 1 installed and all currently published updates to the OS installed. The USB driver is (if I am looking at the right thing in the Device Manager) from Microsoft dated 6/21/2006 version 6.3.9600.17041. The OATH applet version is 0.2.1 and the NEO firmware version is 3.1.2
Author:  Tom [ Mon Oct 13, 2014 10:55 am ]
Post subject:  Re: [QUESTION] Desktop Authenticator does not recognize NEO-
Please download the latest version of the NEO manager from here:

https://developers.yubico.com/yubikey-n ... eases.html


Set the NEO in composite mode ccid-hid and try accessing the gpg applet, does that work?

To test this, just download gpg4win and run gpg --card-status on the command prompt

If you get some information displayed your Yubikey is correctly in CCID mode and recognized. Also check that the windows device manager reports the Yubikey NEO as Microsoft Usbccid smartcard reader WUDF
Author:  STRML [ Wed Oct 22, 2014 9:07 am ]
Post subject:  Re: [QUESTION] Desktop Authenticator does not recognize NEO-
I am seeing a similar error on OS X 10.10. The same NEO works fine with the Android app.

I was having trouble getting yubioath-desktop to install dependencies correctly - pyscard simply refused to play ball - but I found the unlisted .pkg version from Google (why was it removed from https://developers.yubico.com/yubioath- ... /Releases/). The .pkg installed correctly, and more importantly, installed the deps correctly so I can run the yubioath-desktop python libs from the terminal.

When starting up, it looks like the NEO is detected properly - I see "Using reader" and "Yubico Yubikey NEO OTP+CCID". However I am prompted for a password on startup and I do not have one set. "Cancel" or an empty password does not work.
Author:  Tom [ Wed Oct 22, 2014 9:19 am ]
Post subject:  Re: [QUESTION] Desktop Authenticator does not recognize NEO-
pkg got lost in transitioning on new developers.yubico.com website.

We will re-add it.

Unfortunately I have really little bandwidth to work on that project right now, thus if you guys want to submit a pull request you are welcome!
Author:  encryptitall [ Mon Jun 01, 2015 2:09 am ]
Post subject:  Re: [QUESTION] Desktop Authenticator does not recognize NEO-
Using the pre-3.0 Yubikey Neo Manager all 3 modes activated it did not work with the tray applet on Ubuntu Trusty.

After performing _all_ recommendations in this thread, I am now cloggin my network with the installation of 0.5 Gigabyte huge qt4-sdk in order to compile version 3.0 of the neo manager. :evil:

Now I ended up with an egg file which after doing an easy_install indeed does install a tool called "neoman". Starting it yields in version 1.3. Hurray. Now I switched on all three ticks to activate all three different modes - result: The oath applet does still not work! :x


While the YK is an extremely cool and easy-to-use device, which I am actively promiting, let me just openly say that the user experience so far completely sucked on Linux. Hours and hours of troubleshooting, googling and forum thread reading to get this to work, and in the end, it did not.
Page 1 of 2 All times are UTC + 1 hour
Powered by phpBB® Forum Software © phpBB Group
https://www.phpbb.com/