VeriSign links with Microsoft on authentication


VeriSign links with Microsoft on authentication

VeriSign has partnered with Microsoft to deliver authentication services for Windows Server 2003, claiming that it will be cheaper and easier to install than existing offerings.

The partnership builds on a relationship between the companies announced last June when Microsoft and VeriSign said they were teaming up to provide PKI (public key infrastructure) security services for Windows Server 2003.

The authentication services will use and extend Microsoft protocols which VeriSign licensed last year. Users will be able to distribute desktop PKI credentials and include support for a variety of strong, multifactor authentication options such as smart cards and security tokens.

Furthermore, these user authentication products will also work with several Microsoft applications, including secure VPN (virtual private network), wireless Lan access and secured e-mail, VeriSign said. Systems administrators will be able to use Microsoft tools to manage users and provision credentials.

The authentication services will include one of the first reference implementations of the Open Authentication Reference Architecture (Oath), which VeriSign announced earlier this week.

Oath is intended to replace the patchwork of proprietary products for user authentication and provisioning used on the Internet, allowing users to access services on corporate networks and the web seamlessly.

General availability is slated for later this year. Pricing and licensing details were not announced.

Joris Evers writes for IDG News Service

Email Alerts

Register now to receive IT-related news, guides and more, delivered to your inbox.
By submitting your personal information, you agree to receive emails regarding relevant products and special offers from TechTarget and its partners. You also agree that your personal information may be transferred and processed in the United States, and that you have read and agree to the Terms of Use and the Privacy Policy.

COMMENTS powered by Disqus  //  Commenting policy