Yubico Forum

Many corporate types keep telling us Yubikey has to support OATH otherwise they won't adopt it. That adds more cost to Yubikey due to the memory and CPU power required. I wonder what do you think.

* Do you hear people asking you for OATH when you demo Yubikey to them?

* Is Yubikey+OATH nice-to-have or must-have in your use case?

Thanks for comments

Paul

_________________
The YubiKey Server Guy

For a few weeks I've been thinking about how to sell the Yubikey to an enterprise (specifically the one I work for). One challenge I see is the lack of a "enterprise grade" authentication server. What I mean by that is redundant systems so that if a auth server were to crash, or a facility where one is housed were to become unavailable, there would still be one or more backup authentication server available. Further, if anything were to go wrong with the server, there is an expectation that we have a support contract with the vendor.

So that leads to this question: would it be easier to modify the Yubico validation server to support multiple servers, replicated back end data, load balancing and to provide support contracts, or to release a new Yubikey OATH model that can use an existing "enterprise" OATH server? While the OATH authentication server market doesn't appear to be crowed, I think I've found one or two that attempt to meet those requirements.

Moved ECC comment to ECC thread viewtopic.php?p=715#p715

I think that's more of an deployment & operational issue. I've been thinking about adopting the Nagios monitoring framework for Yubico's validation server, beside putting a load balancer to front the traffic from the net when the traffic grows.



Good ideas! Add them into the todo list of Yubico's open-sourced Java and PHP validation servers:

http://code.google.com/p/yubikey-val-server-php/

http://code.google.com/p/yubikey-server-j/

_________________
The YubiKey Server Guy