Showing posts with label ADFS. Show all posts
Showing posts with label ADFS. Show all posts

Azure AD Connect version 1.1.751.0 released for download only

Wednesday, April 18, 2018
Microsoft just published Azure Active Directory Connect version 1.1.751.0. This is a big fix version that resolves two specific issues:

  • Corrected an issue where automatic Azure instance discovery for China (21Vianet) tenants was occasionally failing.
  • For AD FS there was a problem in the configuration retry logic that would result in an ArgumentException stating "an item with the same key has already been added." This would cause all retry operations to fail.
Since these issues only affect a small number of users this build will not be deployed via Auto Upgrade. Affected users will need to download this version directly from the AAD Connect download site.

Read more ...

I'll be speaking at IT/Dev Connections!

Friday, October 20, 2017

I'll be presenting at IT/Dev Connections next week in San Francisco. It'll be nice to have a conference near my home town in the Bay Area.

My session is Take Control Authentication in Office 365.
Microsoft offers several ways for users and admins to authenticate easily and securely to Office 365. In this session you will learn about new advances in claims based and pass through authentication, multi-factor auth, and the controls available for each. With that knowledge, you'll be able to decide which authentication method works best for your organization. We'll also discuss architectures for high availability and disaster recovery. Live demos will bring it all together.
I'm excited to do this presentation, as I've been doing more Identity work than Exchange lately. I hope you can attend this session and others at IT/Dev Connections. Connections is a boutique IT conference with lots of face time and conversations with MVPs and other experts in their fields. I hope you can join me there!

Other MVP experts include Tony Redmond, Chris Goosen, Jaap Wesselous, J. Peter Bruzzese, and others.


Read more ...

Important AD FS Update for Azure AD Connect

Wednesday, March 8, 2017

Microsoft has released Azure Active Directory Connect 1.1.443.0 which includes several bug fixes and new features that your environment will need, especially if you use AD FS:
  • Added support for updating AD FS Farm SSL Certificate
  • Added support for managing AD FS 2016
  • You can now specify existing gMSA (Group Managed Service Account) during AD FS installation
  • You can now configure SHA-256 as the signature hash algorithm for Azure AD relying party trust.

That last bullet point is very important now that the SHA1 algorithm has been cracked, as I wrote last month.

Azure AD Connect makes on-premises and Office 365 directory integration easy and simplifies the management of your on-premises and cloud identity infrastructure.


EXPTA Consulting can help your organization move to the Microsoft cloud or upgrade your existing hybrid infrastructure. Contact us today!
Read more ...

How to Update Certificates for AD FS 3.0

Monday, March 9, 2015
Active Directory Federation Services (AD FS) 3.0 is a server role included in Windows Server 2012 R2. There are several documents and guides for replacing SSL, token-signing, and token-encryption certificates available for AD FS 2.0, but I couldn't find one for AD FS 3.0 so here it is. :)

There are three certificates used by ADFS for SSO:
  1. Service Communications -- This SSL cert is used to encrypt all client connectivity to the AD FS server.
  2. Token-Signing -- This x.509 cert is used to sign the token sent to the relaying party to prove that it indeed came from AD FS.
  3. Token-Decrypting -- This x.509 cert used to encrypt the payload of a SAML token before its encrypted again at the SSL transport layer. It is rarely used.

Replacing the Service Communications Certificate

Normally the Service Communications certificate comes from a trusted third-party CA, like DigiCert or GoDaddy. This is a traditional SSL cert like you would use in IIS for any secure web server. You may use a single-name, subject alternative name (SAN), or wildcard cert for this purpose as long as it's valid and trusted by internal and external AD FS clients.

If you have more than one AD FS server in your environment you will run the second half of these procedures from the primary AD FS server. The changes will replicate to all other AD FS servers in the farm.
  • Request and install a new SSL certificate from a trusted third-party CA. Install this cert and private key in the local computer's Personal store on all AD FS servers in the farm.
  • Logon to each AD FS server and open an elevated PowerShell prompt to run the following commands:
dir cert:\LocalMachine\My
  • Copy the thumbprint for the new SSL certificate you wish to use, then run:
Set-AdfsSslCertificate -Thumbprint thumbprint

If you receive any errors from this cmdlet you either haven't installed the new SSL certificate on all AD FS servers in the farm or you haven't installed the private key for the cert.

Replacing the Service Communications Certificate on WAP Servers

If your organization uses Web Application Proxy (WAP) servers for your AD FS deployment, you'll want to update them with the same SSL certificate.
  • Install the new SSL certificate and private key in the local computer's Personal store on all WAP servers used by AD FS in your environment.
  • Run the following to get the new certificate's thumbprint:
dir cert:\LocalMachine\My
  • Copy the thumbprint and run:
Set-WebApplicationProxySslCertificate -Thumbprint thumbprint
  • Repeat for each WAP server.
  • PowerTip: Use the DigiCert SSL Installation Diagnostics Tool to confirm that the certificate and all intermediate certs are installed correctly. This tool works with any third-party CA certificate, not just DigiCert's.

Replacing the Token-Signing and Token-Decrypting Certificate

The Token-Signing and Token-Decrypting certificates are normally self-signed certificates good for one year, dated from the time the primary AD FS server was installed. The Office 365 portal will warn you when these certs are about to expire and that user access to all Office 365 services will fail.


Although you can use public certs for Token-Signing and Token-Decrypting, I don't recommend it because it's a waste of time and money. You also should not use the same SSL cert that you use for Service Communications for Token-Decrypting or Token-Signing. As mentioned earlier, the Token-Decrypting certificate is rarely used, but I include it here so that Office 365 doesn't warn about it.

NOTE: Be aware that there is an AD FS service outage incurred when the Token-Decrypting or Token-Signing certificates are updated because the relaying parties must update their configuration to expect the new certs. Do this work when users are least impacted by the outage.

Before you renew the Token-Signing and Token-Decrypting certificates I recommend that you increase the AD FS certificate lifetime for self-signed certs.
  • Logon to the primary AD FS server and open an elevated PowerShell prompt. Run the following to configure the AD FS server to generate self-sign Token-Signing and Token-Decrypting certificates that last 100 years and enable Auto Certificate Rollover:
Set-ADFSProperties -CertificateDuration 36500 -AutoCertificateRollover $true
  • These cmdlets will generate new self-signed Token-Signing and Token-Decrypting certificates which will be promoted immediately and then disable auto certificate rollover again. Relay partners will need to update their metadata to accept the new signed claims:
Update-AdfsCertificate -CertificateType Token-Decrypting -Urgent
Update-AdfsCertificate -CertificateType Token-Signing -Urgent
Set-ADFSProperties -AutoCertificateRollover $false 
  • Update the Office 365 metadata using Windows Azure PowerShell:
Connect-MsolService
Update-MsolFederatedDomain -DomainName domain.com -SupportMultipleDomain

  • Remember that you'll need to update other relaying party metadata, if you use them. For example, Yammer on-prem (not Office 365) must be updated manually by Microsoft by opening a support ticket in the Office 365 portal. You will need to supply them with the Token-Signing and Token-Decrypting certificates (minus the private keys).

A Note About WAP Servers

If your organization uses Windows Application Proxy (WAP) servers for your AD FS deployment, there's nothing else you need to do regarding Token-Signing and Token-Decrypting certificates. WAP servers only use the Service Communications SSL cert.

Read more ...

How to Enable RelayState in ADFS 2.0 and ADFS 3.0

Friday, November 7, 2014
RelayState is a parameter of the SAML protocol that is used to identify the specific resource the user will access after they are signed in and directed to the relying party’s federation server. It is used by Google Apps and other SAML 2.0 resource providers.

If RelayState is not enabled in AD FS, users will see something similar to this error after they authenticate to resource providers that require it:

The Required Response Parameter RelayState Was Missing

For ADFS 2.0, you must install update KB2681584 (Update Rollup 2) or KB2790338 (Update Rollup 3) to provide RelayState support. ADFS 3.0 has RelayState support built in. In both cases RelayState still needs to be enabled.

Use the following steps to enable the RelayState parameter on your AD FS servers:

  • For ADFS 2.0, open the following file in Notepad: 
%systemroot%\inetpub\adfs\ls\web.config
  • For ADFS 3.0, open the following file in Notepad:
%systemroot%\ADFS\Microsoft.IdentityServer.Servicehost.exe.config

  • In the microsoft.identityServer.web section, add a line for useRelyStateForIdpInitiatedSignOn as follows, and save the change:
<microsoft.identityServer.web>    ...    <useRelayStateForIdpInitiatedSignOn enabled="true" />    ...</microsoft.identityServer.web>
  • For ADFS 2.0, run IISReset to restart IIS.
  • For both platforms, restart the Active Directory Federation Services (adfssrv) service.
If you're using ADFS 3.0 you only need to do the above on your ADFS 3.0 servers, not the WAP servers.


Read more ...

Chrome or Firefox will not accept credentials when logging in using ADFS server

Friday, February 7, 2014
You may find that Google Chrome or FireFox 3.5+ keeps prompting for authentication when you are redirected to your ADFS 2.0 server.  This is also known to affect Fiddler.  See "AD FS 2.0: Continuously Prompted for Credentials While Using Fiddler Web Debugger" on TechNet.

This happens when Windows Authentication Extended Protection is enabled in IIS on either the ADFS proxy, ADFS back-end server, or both.

Here's how to turn Extended Protection off:

  • Login to the ADFS proxy server and open the Internet Information Services (IIS) Management console.
  • Navigate to the adfs\ls virtual directory under the Default Web Site.

  • Double-click Authentication to open the authentication methods for the ADFS\LS directory.
  • Select Windows Authentication and then click Advanced Settings in the Actions pane.
  • Set Extended Protection to Off.
  • Make sure you do this for all your ADFS proxy and ADFS back-end servers.

Read more ...