...
| Date | Institutional Domain Name | User count (approx) F = Fac, E = Staff S = Student, O = Other, A = Alum, H = Healthcare | How long deployed | Hardware Token Count issued/purchased | Hardware Token Types | non-Yubikey counts issued / purchased | Yubikey counts issued / purchased | Support hours overall / tokens | Self-Service for Token enroll or mgmt Yes / No / Comment | General comments | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | 20171109 | example.edu | 50,000 F, E, O | 1.5 years | 200 / 1000 | yubikey/D100/C100/etc | 100 / 500 | 100 / 500 | 24x7 / m-f 9-5 | Yes - enroll only, no delete | We worried a great deal about tokens and they ended up not being an issue. OR - we don't support hardware tokens at all !!!! | |||||||||
| 2 | 20171109 | harvard.edu | 120,000 F, E, S, A, O | 2.3 years | 2200/3060 | yubikey handful of D100 | 2/10 | 2200/3060 | m-sat 8-6 | No | Initial demand high with service rollout but considerably lower now in steady state. Common use will international travelers unwilling or able to bring cell phone. The logistics of distribution and tracking is painful paired with the pre-config of the secrets. Would be nice if U2F had better adoption and use in non-web apps like VPN clients -T. Gleason | |||||||||
| 3 | 20171109 | northwestern.edu | 50,000 F,E,S,O | 4 years | 15 / 50 | D100 | 50 | 0 / 0 | No | There was plenty of discussion around tokens, but, other than a few cases, there is really no demand in the community. (from Safian, gettes entered) | ||||||||||
| 4 | 20171109 | umbc.edu | 500 F,E | 3 years | 10/20 | D100 | 10/20 | 0/0 | 8-6 m-f | No | We just obtained our site license for faculty and staff - thus the low enrollment. We will be doing our best to discourage token use. With that said, our IT department will most likely pick up the cost of any token purchases. | |||||||||
| 5 | 20171109 | smu.edu | 3,200 F,E | 2 years | 2/50 | YubiKey 4 | 0/0 | 2/50 | No | We've seen almost no interest in tokens after rollout to 100% of employees. Changes may come when we begin requiring Duo logon for students. We will soon begin an effort to increase the percentage of Duo Push authentications which is currently at 64%. Voice at 29%. | ||||||||||
| 6 | 20171110 | uncg.edu | 540/20,000 F, E, S | 2 years | 72/250 | D-100, handful of yubikey | 68/246 | 4/4 | 24x7 / m-f 9-5 | No for OTP, Yes for U2F | Our 2FA program is largely opt-in (so far). Initially there was a ton of demand for tokens as the University elected to not provide devices recommending the Duo Mobile's Push as the preferred mechanism and employees (thought they) wanted separation between work/personal life (we does not own/issue mobile phones). After answering by creating a token program with our ID center avail for purchase, there have been very few takers. The D-100 token was picked for ease of secrets handling and security's desire for a fully out of band token with no dependency on an internet connected device. | |||||||||
| 7 | ||||||||||||||||||||
| 8 | ||||||||||||||||||||
| 9 | ||||||||||||||||||||
| 10 | ||||||||||||||||||||
| 11 | ||||||||||||||||||||
| 12 | ||||||||||||||||||||
| 13 | ||||||||||||||||||||
| 14 | ||||||||||||||||||||
| 15 | ||||||||||||||||||||
| 16 | ||||||||||||||||||||
| 17 | ||||||||||||||||||||
| 18 | ||||||||||||||||||||
| 19 | ||||||||||||||||||||
| 20 | ||||||||||||||||||||
| 21 | ||||||||||||||||||||
| 22 | ||||||||||||||||||||
| 23 | ||||||||||||||||||||
| 24 | ||||||||||||||||||||
| 25 | ||||||||||||||||||||
| 26 |