Sharepoint user validating
FIM 2010 R2 SP1 introduces support for Windows Server 2012, and this is something we definitely want to leverage for our Identity Management platform.
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.
All of these are assumed to be in place, and are not covered in this article.
There’s not much point deploying an Id M platform without following fundamental Information Security principals.
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.
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.We will also cover how to prepare Share Point 2013 for the deployment of the FIM Portal, and finally the installation of the Portal itself.This article assumes that you are familiar with the functional decomposition of the FIM product and its logical architecture components.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.