What does validating identity mean
We will also deploy in a least privilege manner, ensuring recommended account restrictions are in place.
First things first, we need our FIM service accounts.
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.
However there are a number of configuration aspects which must be present and correct, and these differ significantly from what would be considered Share Point “best practices” and in some cases supported Share Point configuration.
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.
The FIM Portal works perfectly well today in Share Point 2010, and needs none of the new end user capabilities, or shudder at the thought, a Modern UI.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.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.