SafeNet Authentication Client Using SafeNet Authentication Client CBA for Exchange 2016 with ADFS - Integration Guide

Remote access poses both a security and a compliance challenge to IT organizations. The ability to positively identify users (often remote users) requesting access to resources is a critical consideration in achieving a secure remote access solution. Deploying remote access solution without strong authentication is like putting your sensitive data in a vault (the datacenter), and leaving the key (user password) under the door mat.

The integration environment that was used in this document is based on the following software versions:

• SafeNet Authentication Client (SAC) - 10.3
• Microsoft Exchange server 2016
• Microsoft AD FS 2012 R2
• Microsoft Active Directory & Certificate authority