Configure two-factor authentication in Skype for Business Server 2015
Topic Last Modified: 2015-06-12
The following sections describe the steps necessary to configure two-factor authentication for your deployment. For more information about Two-factor authentication, see Enabling Office 365 multi-factor authentication for online administrators - Grid User Post.
The following steps describe how to configure an Enterprise Root CA to support Smart Card Authentication:
For information on how to install an Enterprise Root CA, see Install an Enterprise Root Certification Authority.
Log in to the Enterprise CA computer using a Domain Admin account.
Launch System Manager, and verify that the Certificate Authority Web Enrollment role is installed.
From the Administrative Tools menu, open the Certification Authority management console.
In the Navigation pane, expand Certification Authority.
Right click on Certificate Templates, select New, then select Certificate Template to Issue.
Select Enrollment Agent, Smartcard User, and Smartcard Logon.
Right click on Certificate Templates.
Open the properties of the Smartcard User template.
Click on the Security tab.
Change the permissions as follows:
Add individual user AD accounts with Read/Enroll (Allow) permissions, or
Add a security group containing smart card users with Read/Enroll (Allow) permissions, or
Add the Domain Users group with Read/Enroll (Allow) permissions
One factor to consider when deploying two-factor authentication and smart card technology is the cost of implementation. Windows 8 provides a number of new security capabilities, and one of the most interesting new features is support for virtual smart cards.
For computers equipped with a Trusted Platform Module (TPM) chip that meets specification version 1.2, organizations can now get the benefits of smart card logon without making any additional investments in hardware. For more information, see Using Virtual Smart Cards with Windows 8.To Configure Windows 8 for Virtual Smart Cards
Log in to the Windows 8 computer using the credentials of a Skype for Business-enabled user.
At the Windows 8 Start screen, move your cursor to the bottom right corner of the screen.
Select the Search option, and then search for Command Prompt.
Right click on Command Prompt, and then select Run as Administrator.
Open the Trusted Platform Module (TPM) Management console by running the following command:
From the TPM management console, verify that your TPM specification version is at least 1.2
Note: If you receive a dialog stating that a Compatible Trust Platform Module (TPM) cannot be found, verify that the computer has a compatible TPM module and that it is enabled in the system BIOS.
Close the TPM management console
From the command prompt, create a new virtual smart card using the following command:
TpmVscMgr create /name MyVSC /pin default /adminkey random /generate
Note: To provide a custom PIN value when creating the virtual smart card, use /pin prompt instead.
From the command prompt, open the Computer Management console by running the following command:
In the Computer Management console, select Device Management.
Expand Smart card readers.
Verify that the new virtual smart card reader has been created successfully.
There are generally two methods for enrolling users for smart card authentication. The easier method involves having users enroll directly for smart card authentication using web enrollment, while the more complex method involves using an enrollment agent. This topic focuses on self-enrollment for smartcard certificates.
For more information on enrolling on behalf of users as an enrollment agent, see Enroll for Certificates on Behalf of Other Users.To Enroll Users for Smart Card Authentication
Log in to the Windows 8 workstation using the credentials of a Skype for Business-enabled user.
Launch Internet Explorer.
Browse to the Certificate Authority Web Enrollment page (e.g. https://MyCA.contoso.com/certsrv).
Note: If you are using Internet Explorer 10, you may need to view this website in Compatibility Mode.
On the Welcome Page, select Request a certificate.
Next, select Advanced Request.
Select Create and submit a request to this CA.
Select Smartcard User under the Certificate Template section and complete the advanced certificate request with the following values:
Key Options confirm he following settings:
Select the Create new key set radio button
For CSP, select Microsoft Base Smart Card Crypto Provider
For Key Usage, select Exchange (this is the only option available).
For Key Size, enter 2048
Confirm that Automatic key container name is selected
Leave the other boxes unchecked.
Under Additional Options confirm the following values:
For Request Format select CMC.
For Hash Algorithm select sha1.
For Friendly Name enter Smardcard Certificate.
If you are using a physical smartcard reader, insert the smart card into the device.
Click Submit to submit the certificate request.
When prompted, enter the PIN that was used to create the virtual smart card.
Note: The default virtual smart card PIN value is ‘12345678’.
Once the certificate has been issued, click Install this certificate to complete the enrollment process.
Note: If your certificate request fails with the error “This Web browser does not support the generation of certificate requests,” there are three possible ways to resolve the issue:
Enable Compatibility View in Internet Explorer
Enable the Turn on Intranet settings option in Internet Explorer
Select the Reset all zones to default level setting under the Security tab in the Internet Explorer options menu.
The following section describes how to configure Active Directory Federation Services (AD FS 2.0) to support multi-factor authentication. For information on how to install AD FS 2.0, see AD FS 2.0 Step-by-Step and How To Guides.
|When installing AD FS 2.0, do not use the Windows Server Manager to add the Active Directory Federation Services role. Instead, download and install the Active Directory Federation Services 2.0 RTW package.|
Log in to the AD FS 2.0 computer using a Domain Admin account.
Start Windows PowerShell.
From the Windows PowerShell command-line, run the following command:
Establish a partnership with each server that will be enabled for passive authentication by running the following command, replacing the server name specific to your deployment:
Add-ADFSRelyingPartyTrust -Name SfBPool01-PassiveAuth -MetadataURL https://SfBpool01.contoso.com/passiveauth/federationmetadata/2007-06/federationmetadata.xml
From the Administrative Tools menu, launch the AD FS 2.0 Management console.
Expand Trust Relationships > Relying Party Trusts.
Verify that a new trust has been created for your Skype for Business Server.
Create and assign an Issuance Authorization Rule for your relying party trust using Windows PowerShell by running the following commands:
$IssuanceAuthorizationRules = '@RuleTemplate = "AllowAllAuthzRule" => issue(Type = "http://schemas.microsoft.com/authorization/claims/permit", Value = "true");'
Set-ADFSRelyingPartyTrust -TargetName SfBPool01-PassiveAuth -IssuanceAuthorizationRules $IssuanceAuthorizationRules
Create and assign an Issuance Transform Rule for your relying party trust using Windows PowerShell by running the following commands:
$IssuanceTransformRules = '@RuleTemplate = "PassThroughClaims" @RuleName = "Sid" c:[Type == "http://schemas.microsoft.com/ws/2008/06/identity/claims/primarysid"]=> issue(claim = c);'
Set-ADFSRelyingPartyTrust -TargetName SfBPool01-PassiveAuth -IssuanceTransformRules $IssuanceTransformRules
From the AD FS 2.0 Management console, right click on your relying party trust and select Edit Claim Rules.
Select the Issuance Authorization Rules tab and verify that the new authorization rule was created successfully.
Select the Issuance Transform Rules tab and verify that the new transform rule was created successfully.
There are two possible authentication types that can be configured to allow AD FS 2.0 to support authentication using smart cards:
Forms-based authentication (FBA)
Transport Layer Security Client Authentication
Using forms-based authentication, you can develop a web page that allows users to authenticate either by using their username/password or by using their smart card and PIN. This topic focuses on how to implement Transport Layer Security Client Authentication with AD FS 2.0. For more information about AD FS 2.0 authentication types, see AD FS 2.0: How to Change the Local Authentication Type.To Configure AD FS 2.0 to Support Client Authentication
Log in to the AD FS 2.0 computer using a Domain Admin account.
Launch Windows Explorer.
Browse to C:\inetpub\adfs\ls
Make a backup copy of the existing web.config file.
Open the existing web.config file using Notepad.
From the Menu bar, select Edit and then select Find.
Search for <localAuthenticationTypes>.
Note that there are four authentication types listed, one per line.
Move the line containing the TLSClient authentication type to the top of the list in the section.
Save and Close the web.config file.
Launch a Command Prompt with elevated privileges.
Restart IIS by running the following command:
IISReset /Restart /NoForce
The following section describes how to configure Skype for Business Server 2015 to support passive authentication. Once enabled, users who are enabled for two-factor authentication will be required to use a physical or virtual smart card and a valid PIN to sign in using the Skype for Business client.
|It is strongly recommended that customers enable passive authentication for Registrar and Web Services at the service level. If passive authentication is enabled for Registrar and Web Services at the global level, it will likely result in organization-wide authentication failures for users who are not signing in with the supported desktop client.|
The following steps describe how to create a custom web service configuration for Directors, Enterprise Pools, and Standard Edition servers that will be enabled for passive authentication.To create a custom web service configuration
Log in to your Skype for Business Server 2015 Front End server using a Skype for Business administrator account.
Launch the Skype for Business Server Management Shell.
From the Skype for Business Server Management Shell command-line, create a new Web Service configuration for each Director, Enterprise Pool, and Standard Edition server that will be enabled for passive authentication by running the following command:
New-CsWebServiceConfiguration -Identity "Service:WebServer:SfBPool01.contoso.com" -UseWsFedPassiveAuth $true -WsFedPassiveMetadataUri https://dc.contoso.com/federationmetadata/2007-06/federationmetadata.xml
Warning: The value for the WsFedPassiveMetadataUri FQDN is the Federation Service Name of your AD FS 2.0 server. The Federation Service Name value can be found in the AD FS 2.0 Management Console by right-clicking on Service from the navigation pane and then selecting Edit Federation Service Properties.
Verify that the UseWsFedPassiveAuth and WsFedPassiveMetadataUri values were set correctly by running the following command:
Get-CsWebServiceConfiguration -identity "Service:WebServer:SfBPool01.contoso.com" | format-list UseWsFedPassiveAuth, WsFedPassiveMetadataUri
For clients, Passive Authentication is the least preferred authentication method for webticket authentication. For all Directors, Enterprise Pools, and Standard Edition servers that will be enabled for passive authentication, all other authentication types must be disabled in Skype for Business Web Services by running the following cmdlet:
Set-CsWebServiceConfiguration -Identity "Service:WebServer:SfBPool01.contoso.com" -UseCertificateAuth $false -UsePinAuth $false -UseWindowsAuth NONE
Verify that all other authentication types have been successfully disabled by running the following cmdlet:
Get-CsWebServiceConfiguration -Identity "Service:WebServer:SfBPool01.contoso.com" | format-list UseCertificateAuth, UsePinAuth, UseWindowsAuth
When certificate authentication is disabled for Skype for Business Web Services, the Skype for Business client will use a less preferred authentication type, such as Kerberos or NTLM, to authenticate to the Registrar service. Certificate authentication is still needed to allow the client to retrieve a webticket, however, Kerberos and NTLM must be disabled for the Registrar service.
The following steps describe how to create a custom proxy configuration for Edge Pools, Enterprise Pools, and Standard Edition servers that will be enabled for passive authentication.To create a custom proxy configuration
From the Skype for Business Server Management Shell command-line, create a new proxy configuration for each Skype for Business Server 2015 Edge Pool, Enterprise Pool, and Standard Edition server that will be enabled for passive authentication by running the following commands:
New-CsProxyConfiguration -Identity "Service:EdgeServer:EdgePool01.contoso.com" -UseKerberosForClientToProxyAuth $False -UseNtlmForClientToProxyAuth $False
New-CsProxyConfiguration -Identity "Service:Registrar:SfBPool01.contoso.com" -UseKerberosForClientToProxyAuth $False -UseNtlmForClientToProxyAuth $False
Verify that all other proxy authentication types have been successfully disabled by running the following command:
Get-CsProxyConfiguration -Identity "Service:Registrar:SfBPool01.contoso.com" | format-list UseKerberosForClientToProxyAuth, UseNtlmForClientToProxyAuth, UseCertifcateForClientToProxyAuth