Info to give vendors on what they should tell us about. |
This section gives potential vendors a brief summary of what we are doing and what we want.
Virginia Tech is in the process of issuing smart cards/tokens to all faculty and staff (approximately 6500 users). The Aladdin eToken was selected for this phase of the project. The scope of this phase is fairly limited and only requires support for signing documents with a web browser under MS Windows, Linux, and OS X. Evaluation of smart devices will be an ongoing process. We would like to support several devices if practical. Our current expectation is to replace the Aladdin eTokens in three to five years and we would like to conduct small deployments of alternate devices during that time. The university has 25,000+ students. While there is no firm plan to distribute smart devices to them at this time, experience with the current phase of deployment may demonstrate enough benefit that this will occur. To the extent practical, we want: * a commodity product, i.e. standards-based and as interchangeable with similar products as practical. * vendor, platform, and operating system neutrality. * open availability of technical information, e.g. developer's web site or wiki. * support in open-source products such as OpenSSL and OpenSC, and GnuPG Also note that: * Our token management system is a locally developed application which interfaces with a backend OpenCA certification authority to support personal certificate enrollment. Please include Phil Benchoff (benchoff@vt.edu) and Frank Galligan (frankg@vt.edu) on any follow up communications related to this project. |
This section outlines the topics we would like covered in a more detailed presentaion from a vendor.