Yubico Forum

I require the use of ActivClient smartcard middleware for use with government websites. I found out the hard way that it somehow takes sole precedence of any smartcards in the system when plugged in. Basically, if it detects a smartcard, which the Neo presents itself as, it will prevent using the challenge+response method. I was able to stop the ActivClient service to make the Neo work properly (it also prevents writing configurations to the Neo). With the service stopped I can use the Neo to log in properly. However, the service is online again when I restart the computer. I accidentally completely locked myself out this way.

I need to keep ActivClient, and I can't figure out any way to get it to ONLY read a CAC/smartcard.

Has anyone else had this problem or know of a work-around?

Do you use the NEO in smartcard mode?

Switch to Yubikey only if you don't need the smartcard part, ( mode 0 )

_________________
-Tom

I think it has to be in order to use it properly with Android. I did not force into SC mode myself, so I'm assuming the software to set it up with Android did it.

No, to enable the SmartCard portion of the NEO you need to manually enable the mode 82 and powercycle the device.

To use the NFC interface with the Yubikey features (OTP, HOTP, CR) you do not need the smartcard.

_________________
-Tom

The instructions I followed specifically had me enable mode 82. My work around for this is to enable and disable the smart-card service when I need it. Seems to work fine that way, so long as I don't lock the computer during the time that it's enabled. I've also decided that I'm just going to create a VM for all my government stuff, and just install the CAC software on that.

After tracing my steps to setup my Neo, I seem to have been mistaken. I think I ended up enabling Mode 82 due to a misconception of my original problem (caused by ActivClient) when I was looking for solutions.