Microsoft FIM ( Frontend Identity Manager) is a very popular enterprise application that. Allows users to be created and managed by automating provisioning. And de-provisioning of users in Microsoft Active Directory. FIM comes with a variety of out-of-the-box extensions connectors that allow you to connect FIM to. Other systems (like catalogs for users that are external business coach to the user) and a range of web-based services. When the connectors provided by the manufacturer are not enough, you can develop an individual. Management Agent (MA) that FIM can use with the .NET framework. .
It is basically the sole source of information regarding the creation of Extensible Connectivity Management Agents (ECMA). However, the issue is that the source does not include a comprehensive guideline to create ECMAs. And the code example, though giving a complete code list for the management agent, does not provide all the information needed to create. Actually, the code example is a single very services simple example that is a simple example of ECMA 2.2 agents. Moreover, there are a few locations in this sample that need further explanation.
Process for creating FIM MAs is not well described
I was recently able to help connect FIM to an external system that contained a MySQL users database. There isn’t an out-of-the-box FIM connector for MySQL so we needed to develop. Our own customized life coach in my area management software. As I worked on this task, I discovered that the process for creating FIM MAs is not well services described. It is the is a reference and this example is basically the sole source of information. Regarding the creation of Extensible Connectivity Management Agents (ECMA). However,
The issue is that the source does not include a comprehensive guideline to create ECMAs, and the code example, though giving a complete code list for the management agent, does not provide all the information needed to create. Actually, the code example is a single very simple example that is a simple example of ECMA 2.2 agents. Moreover, there are a few locations in this sample that need further explanation.
Provide all the information needed to create
I’m not going to re-read Microsoft document however I do want to share a few of the things that I have learned while the process of creating FIM MA and that aren’t obvious from the provided samples of code.
1. GetSchema and GetImportEntries need to be the same. GetSchema returns a complete set of columns that are accessible for the FIM operator (i.e. the person configuring MA within FIM) to choose to import and map into the AD metaverse
