Presenting Exchange 2019 With WAP and ADFS

KB ID 0001546

Problem

I’ve used WAP (Web Application Proxy) to present Remote Desktop Services before, but never for Microsoft Exchange. It came up as a possible requirement for a client this week, so I thought I’ll work it out on the bench. here’s the topology;

ADFS Exchange WAP Topology

Exchange: Exchange 2019 Standard

Server OS: Server 2019 Datacenter

Solution – Step 1 Deploy ADFS

If you are going to use ‘self signed’ certificates then before you deploy ADFS, (Active Directory Federation Services,) you will want to Deploy Certificate Services. Here I’m going to use a self signed wildcard certificate. In production however, I would suggest you use a wildcard certificate signed by a public CA authority. (Click the Certificate link above).

To deploy ADFS simply follow the steps in this article;

Deploy Active Directory Federation Services

Solution – Step 2 Configure ADFS for OWA and ECP

There are a few ‘Web’ Services that Exchange provides, Outlook Web App, and Exchange Control Panel (Exchange Administration Centre), are ‘tied’ together and need to be presented in the same way, so we will cover them first.

IMPORTANT: You need to change OWA and ECP together, BE AWARE that means your Exchange Administration panel will be secured by ADFS, (and ADFS ONLY!) So you may need to change the way you do Exchange administration, (or leave one Exchange server without ADFS secured ECP for internal management).

So you create the ‘trusts’ for OWA and ECP in ADFS, then the WAP server will use those ‘trusts’. CARRY OUT THE FOLLOWING PROCEDURE TWICE, once for OWA, and once for ECP.

Open the ADFS management console > Relying Party Trusts > Add Relying Part Trust > (With ‘claims aware’ selected) > Next.

ADFS Relying Claims Aware Trust

Enter data about the relying party manually > Next.

Manual Relying Part Trust

Give the trust a name e.g. ‘Outlook Web App’ > Next.

OWA Publish ADFS Trust

Next

Exchange 2019 Publish with WAP

Enter the ORL for OWA (with a trailing slash) e.g. https://mail.domainname.com/owa/

ADFS URL for Exchange

Permit everyone > Next.

ADFS WAP Trust Settings

Next

Review ADFS Settings

Close.

Configure Claims Issuance

NOW REPEAT THE ABOVE PROCEDURE FOR ECP (https://mail.domain.com/ecp/)

ADFS Create “Claims Issuance Policies”

Why are you doing this? This allows you to connect to the WAP server and enter your username and password ONCE. To enable you to only supply usernames and passwords once, you need two things, 1) Claims Issuance Policies, that can query AD and collect your UPN and check your password, and 2) Exchange set to allow ADFS authentication, (instead of the usual basic, and ‘forms based’ authentication is uses for OWA and ECP out of the box).

AGAIN CARRY THIS PROCEDURE OUT TWICE, ONCE FOR OWA AND ONCE FOR ECP

From ADFS Management > Relying Party Trusts > Select your OWA Trust > Edit Claim Issuance Policy > Add Rule.

Configure Claims Issuance

Select ‘Send claims using a custom rule’ > Next.

ADFS Claims Rule

Client Rule Name: AD-User

Custom Rule:

c:[Type == "http://schemas.microsoft.com/ws/2008/06/identity/claims/windowsaccountname", Issuer == "AD AUTHORITY"] => issue(store = "Active Directory", types = ("http://schemas.microsoft.com/ws/2008/06/identity/claims/primarysid"), query = ";objectSID;{0}", param = c.Value);

Click ‘Finish’.

Claims AD User Rule

Add a second rule > Again choose ‘Send Claims Using a Custom Rule’ > Next.

ADFS Custom Rule

Client Rule Name: AD-UPN

Custom Rule:

c:[Type == "http://schemas.microsoft.com/ws/2008/06/identity/claims/windowsaccountname", Issuer == "AD AUTHORITY"] => issue(store = "Active Directory", types = ("http://schemas.xmlsoap.org/ws/2005/05/identity/claims/upn"), query = ";userPrincipalName;{0}", param = c.Value);

Click ‘Finish’.

ADFS UPN Rule

You should end up with something like this;

Issuance Transform. Rules

NOW REPEAT THIS PROCEDURE FOR THE ECP

Solution – Step 3 Deploy and Configure WAP

Firewall Requirements

  • The WAP server either needs a Static public IP address that is registered in public DNS to the URLS you will be pointing to it, or HTTPS port forwarding form the firewalls outside IP address to the internal IP of the WAP server, (if you don’t have spare public IP addresses).
  • WAP Server requires TCP Port 443 (HTTPS) open TO it from the outside world.
  • WAP Server requires TCP Port 443 (HTTPS) open FROM it to BOTH the exchange server and the ADFS Server.

Installing Web Application Proxy

To be honest, this is pretty simple, the server itself does not have to be a domain member (which is good for a DMZ server!) For productions I’d disable the local administrator account and harden the server somewhat also. Make sure you have a copy of your wildcard certificate on this server also.

Server Manger > Manage > Add Roles and Features > Next > Next > Next > ‘Remote Access’ > Next > Next > Next > “Web Application Proxy” > Next > Install

Install Web Applicaiton Proxy

Or use the following PowerShell;

Install-WindowsFeature Web-Application-Proxy -IncludeManagementTools

Launch the post deployment configuration wizard > Next.

Configure Web Applicaiton Proxy

Enter the FQDN of your ADFS Server, and administrative credentials > Next > Select Your Wildcard Certificate > Next.

Connect WAP to ADFDS Server

Configure > Close.

Configure WAP 2019

All being well the Remote Access management console should open and should show ‘All Green’ on the Operational Status.

WAP Operational Status

Configure Web Application Proxy for OWA and ECP

Navigate to > Configuration > Web Application Proxy > Publish > Next.

WAP Publish an Application

Select Active Directory Federation Services > Next > Select ‘Web and MSOFBA > Next.

WAP Publish Outlook Web App

Select the ‘Relying Trust’ object that WAP can see for Outlook Web app > Next > Give the Published Rule a Name > Set the Public URL > Select the wildcard certificate > Set the Backend URL > Next.

WAP Publish Outlook Web App ADFS

Publish > Close.

WAP 2019 Publish Outlook Web App ADFS

REPEAT TO PUBLISH ECP

When you have finished it should look something like this;

WAP 2019 Publish Exchange

x

Solution – Step 4 Configure Exchange for ADFS Authentication

Your Exchange needs a copy of the ADFS Signing certificate, this certificate is a ‘self signed’ certificate created on the ADFS server itself, you can find it here;

Locate ADFS Signing Certificate

By Default this certificate only lasts a year, and will need to be manually imported onto Exchange, you can change the certificate duration by suing the following PowerShell and changing the Day value, (in this example to three years).

Change ADFS Certificate duration

Exporting the ADFS Signing Certificate

With the certificate selected, navigation to the ‘Details‘ tab > Copy to File > Follow the instructions, (accept the defaults).

Export ADFS Signing Certificate

Importing the ADFS Signing Certificate Into Exchange

Physically copy the exported certificate to the Exchange server, and double click it > Install Certificate > Local Machine > Next > Place Into the Following Store > Trusted Root Certification Authorities > Next > Finish.

Import ADFS Signing Certificate

Now the certificate has been imported you need to get its thumbprint, open and Exchange Administration Console, and issue the following command. locate the ADFS certificate and copy its thumbprint to the clipboard.

Set-Location Cert:\LocalMachine\My; Get-ChildItem | Format-List FriendlyName,Subject,Thumbprint

Locate ADFS Certificate Thumbprint

 

Set that certificate as the ADFS certificate for your mail organisation with the following command;

Set-OrganizationConfig -AdfsIssuer https://{ADFS-FQDN}/adfs/ls/ -AdfsAudienceUris "{OWA-URL}","{ECP-URL}" -AdfsSignCertificateThumbprint "{Thumbprint}"

Set Exchange ADFS Certificate

Finally you need to set the OWA and ECP virtual directories to accept ADFS authentication, then restart the IIS services, to make the changes take effect.

Set-EcpVirtualDirectory -Identity "EX-SERVER\ecp (Default Web Site)" -AdfsAuthentication $true -BasicAuthentication $false -DigestAuthentication $false -FormsAuthentication $false -WindowsAuthentication $false


Set-OwaVirtualDirectory -Identity "EX-SERVER\owa (Default Web Site)" -AdfsAuthentication $true -BasicAuthentication $false -DigestAuthentication $false -FormsAuthentication $false  -WindowsAuthentication $false

net stop was /y

net start w3svc

 

In Set Exchange OWA and ECP for ADFS

In PART TWO we will publish Outlook Anywhere, Active Sync, EWS, OAB, MAPI and Autodiscover.

Related Articles, References, Credits, or External Links

NA

Author: PeteLong

Share This Post On

7 Comments

  1. Minor typo fix for others benefit.

    This command
    Set-Location Cert:\LocalMachine\My; Get-ChildItem | Format-List FriendlyName,Subject,Thumbprint

    Should be this
    Set-Location Cert:\LocalMachine\root; Get-ChildItem | Format-List FriendlyName,Subject,Thumbprint

    Post a Reply
  2. Great Article, have you created part 2 yet?

    Post a Reply
    • Yes click the words PART TWO 🙂

      P

      Post a Reply
  3. Hi.
    Did you ever get across that on 2019 WAP server this registry key must be enabled:
    HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionInternet SettingsWinHttpEnableDefaultHttp2 Value: 0

    I had some issues publishing Exchange services with WAP,ADFS on OS2019 and that key did the trick.

    Post a Reply
    • It didn’t trip me up but I’ll publish it here for completeness, and further comments.

      Post a Reply
      • Sounds great. Me on other hand ended with replacing WAP2019 with WAP2016 due to this http/2 bug on WAP2019.
        Unfortunatelly after you add that registry key http/2 stops working on WAP for publishing http/2 web application. What is even worst if you delete that key and reboot WAP2019 server http/2 still stays blocked. It looks like ireversible and as we need http2 support on reverse proxy we have downgraded to wap2016 :/

        Post a Reply

Leave a Reply to Driper Cancel reply

Your email address will not be published. Required fields are marked *