Aug 212014
 

It’s been over two years since my last foray into the murky waters of Active Directory Federation Services (ADFS) 2.0 and it came past due for a return to claims-based authentication and federation.

My previous journeys were somewhat chronicled here and here.  This time around though, I’m going to be focusing on the latest and greatest – meaning Windows Server 2012 R2 (with update), which has been a far more pleasant journey thus far.

I literally started from scratch, because I rather like the environment to be clean before establishing a baseline configuration.  From my earlier article:

so if you’re going to do this properly, get your certificates sorted out up front.  My approach is to install and configure an Enterprise Certificate Authority and issue certificates from there.  Then, it’s just a matter of trusting the root CA (signing) certificate in your environment, and your cert chain should be valid

I’m excited to say I took my own advise and started with the basics first.  As you may recall from my earlier writing, my preferred scenario architecture is the segregation of external and internal entities by way of separate Active Directory forests.

As last time, I’m working predominantly with an initial set of four separate virtual servers, configured as follows:

image

Using an Enterprise CA, I trust the root CAs and then issue certificates as needed, and manage the DNS within each Active Directory forest.  This time around I fully configured the CAs in both domains for web enrolment and device enrolment as well as updating group policy to include the Enrolment Policy locations.

 

image

I also added the Root CAs of each domain to the Trusted Root Certificate store in the opposite domain’s DC (where AD FS is located) so that the federation Uris would be valid when the trusts were established.

Believe it or not, this doesn’t take very long to set up.  Configuring each domain at the same time (in parallel), I had most of the configuration working and tested in about an hour or so.  Having done it many times before, I knew the correct order to install and configure which makes a huge difference.

Installing IIS on the CA server also means you can avoid having to install IIS on the domain controller server, which is a nice win in terms of resource minimisation. 

Since we’re dealing with a few certificates here and there, it’s important to remember that clients/machines that do not trust the root CA signing certificate will experience warnings or other inconveniences – in other words, don’t do this in a Production environment unless it’s only used solely in-house, where you can deploy the CA signing certificate into the trusted root CA stores. 

External AD FS installations should always be signed using a certificate from an external (public) CA like https://www.startssl.com which offers free class-1 certificates.

image
Certificate Path

My Desired Outcome

What I want to be in a position to do is to offer users a choice of realms:

image

For the sake of keeping things clear, I’ve labelled the relying parties to indicate which domain they live in, but you probably would label the DMZ as ‘External Users’.

What should happen, once a user has authenticated, is that their subsequent requests to claims-aware applications shouldn’t require any further authentication, and their identity should be available across both environments.

Generating Valid Certificates – The Low Effort Way

Another tip – the AD FS installation expects a certificate (plus private key) with the common name of the ADFS service you’re going to configure to be in the .pfx format.

if you want a fast way of generating a web server certificate and you have an Enterprise CA installed and configured within the domain, you can switch to IIS Manager and request a Domain Certificate when viewing the server features (under Server Certificates):

image

Here you can add the common name and friendly names

imageimage

When you’ve entered the information, the wizard will go off and request a Web Server certificate based on the common name, and then will automatically store it in the Computer Account’s Certificate store.  You can fire up MMC and add the Certificates snap in (FIle –> Add/Remove Snap In) making sure you select ‘Computer account’ along the way:

imageimage

Once the certificate is located, you can simply export it including the private key.  Just move the exported .pfx file to the ADFS host, and you’re ready to install with a valid certificate.

A word about ADFS installation

I’m not going to go into detail about how to set up AD FS 3.0 itself, the existing documentation on the Internet is quite accurate, and honestly, if you’ve established the environment correctly, it’s really not tricky to do.  In Windows Server 2012 R2, ADFS 3.0 is a bona fide server role (in 2008/R2 the server role was ADFS 1.0/1.1, 2.0 was a separate download & install).

Sanity Checking the ADFS configuration

As mentioned in an earlier post, a quick browse to the following location: https://<your adfs location>/federationmetadata/2007-06/federationmetadata.xml should yield a metadata response:

image

Summary

This was just a brief intro to the environment I’ve configured, I’ll be going into more detail about how to live in a claims-aware environment in subsequent articles.

Apr 042014
 

At the moment the annual Microsoft BUILD conference is currently under way in San Francisco in the United States.  This is a time when Microsoft typically unveils major changes to its platforms and other major products – this conference sort of replaces the old Platform Developer Conference (PDC) from ye olden days. 

A highlight this year (amongst many) has been the release of a major Windows 8.1 update which remedies some of the criticisms which have been levelled at the Windows 8 platform since its release.

From the associated KB article which compliments the update:

Improvements

  This update includes the following new features and improvements:

  • Enables a more familiar mouse and keyboard functionality for modern apps and
           controls.
  • Improves the web application compatibility of the Internet Explorer 8 emulation
           mode in Internet Explorer 11 F12 Developer Tools.
  • Increases performance and reliability when you use multi-display configurations for
           portrait-first device experiences.

Which doesn’t say a whole lot.. I’m going to try and find out more about what’s in the update.

The update is currently available to MSDN/TechNet subscribers but will be available to all from April 8.  The version available via MSDN subscriptions is actually a zip archive of a bunch of Windows Update modules, as you can see below.  There are also full ISOs that contain Windows 8.1 + the update, if you plan on a fresh install.

image

Installing them, one by one, takes a while – particularly the update which is over 700mb in size.

image image

Once you finish – after a reboot per module!  You should have the latest edition of Windows 8.1.  I only finished the installation process this morning, so I haven’t had much time to poke around.  The “boot straight to desktop” feature can be changed by right clicking the taskbar and opening the properties dialog:

image

I’m still not sure if this update is supposed to implement the rumoured new start menu or not – from my initial experience, the “star button” still brought up the old formerly-known-as-metro user interface.

Update:

One frequently requested feature — the return of the Start menu button — isn’t part of the new Windows 8.1 release. But it is coming back…some day. Microsoft said it is planning a future update that will bring back a more traditional Start Menu features, as well as the ability to run Modern apps in a window on the desktop.  – Source

So I guess we’ll wait a little longer for the return of the start menu.

image

A quick look at the version dialog – we’re officially running at Ver 6.3 (Build 9600) although the copyright seems out of date (2013?).

I’m also hearing of a term called “Modern apps” to describe Metro apps.  I’m not sure I like that term..

Further Reading

Here’s more on the Windows 8.1 Update: http://www.zdnet.com/microsofts-windows-8-1-update-what-windows-8-should-have-been-from-the-start-7000027976/

The KB attached to the main update (KB2919355) can be found here.

Hints on how to verify you have legitimate copies of the ISOs/update modules.

Here’s some more info on the changes: http://money.cnn.com/2014/04/02/technology/windows-8-update/index.html