Validating identity problem in wireless network
As we know the FIM Portal is based upon Share Point and installs into an existing site collection, thus Share Point is a pre-requisite for the FIM Portal.
The problem is however that Share Point 2010 doesn’t run on Windows Server 2012 yet, for that we need to wait for Share Point 2010 Service Pack 2.However in the journey to the cloud this model is effectively being deprecated in favour of the loosely coupled, off box approach to customization (a.k.a. Of course aligning such disparate strategy across wildly different release cycles is impossible, and it’s both unfeasible and unnecessary for the FIM Portal to be re-implemented at this stage in line with the new world order.The harsh reality is that Share Point 2013 in and of itself offers no value whatsoever in terms of functionality for the FIM Portal.For many years this approach was promoted by Microsoft and leveraged across many products.Instead of the FIM team building out their own hosting infrastructure and site plumbing, they built a bunch of customizations on top of Share Point.This post is not intended to introduce those concepts and therefore is intended for FIM practitioners more so than Share Point professionals new to FIM.
We will be focusing almost exclusively on the FIM Service and Portal components in this article and not talking to the FIM Sync service, Reporting or Certificate Management.
Second are the various things that Share Point 2013 does or promotes which FIM doesn't like.
The best example of this is that the FIM Portal requires the use of Classic Authentication mode (which is deprecated in Share Point 2013). These two traits make something that should be straightforward a bit more “interesting”. Tech Net leaves a lot to be desired here (which is unusual for FIM documentation) including errors in scripts and so on, so this article represents a tested, repeatable and reliable cheat sheet for deployment of the FIM Portal on Share Point 2013.
The flies in the ointment are a couple of pretty common Share Point traits.
Firstly Share Point’s overall addressing architecture along with some shockingly bad deployment guidance which focuses primarily on small scale, often single server deployments.
Whilst coming soon, those building Id M solutions now face either a mix of host operating systems for the various FIM components, or a move to Share Point 2013.