This section needs to be expanded. However, documentation work is similar to the development work in that it takes time and that it needs funding.
ConnId Result Handlers
Those "result handlers" are an artifact of an original original Identity Connector Framework over-engineering. The handlers are supposed to assist connectors by implementing "mechanism" that the connector or resource does not support - such as search result filtering, data normalization and so on. However, those handler are generic and they know nothing about the particulars of the resource that the connector connects to. Therefore in vast majority of cases those handlers just get into the way and they distort the data. Good connectors usually do not need those handlers at all. Unfortunately, these handler are enabled by default and there is no way for a connector to tell the framework to turn them off. The handlers needs to be explicitly disabled in the resource configuration.
<icfs:resultsHandlerConfiguration> <icfs:enableNormalizingResultsHandler>false</icfs:enableNormalizingResultsHandler> <icfs:enableFilteredResultsHandler>false</icfs:enableFilteredResultsHandler> <icfs:enableAttributesToGetSearchResultsHandler>false</icfs:enableAttributesToGetSearchResultsHandler> </icfs:resultsHandlerConfiguration>
Date and Time Formats
In a normal case all timestamps in midPoint are in W3C DateTime format. MidPoint converts all the date/time values to this format. However, there is one problem when it comes to the connectors. The ConnId framework does not have any way how to express date/time information in the schema. ConnId framework is representing date/time information as (long) integers in UNIX timestamp format. Therefore by default even LDAP timestamps are converted to UNIX timestamps. As midPoint does not know that this is a date/time information it cannot properly convert this to W3C dateTime format.