I want the delta import to run immediately after the export without having to schedule it to run on its own. Is there a way I can trigger the delta import from the end of the Export script?

I did see something on the Google Apps Connector topic about import-after-export but can't see any such setting in the IdB 5 UI.

I have an IdB Powershell connector talking to Office 365. One of the IdB schema attributes is “Alumni” (Boolean flag). I populate this on import from O365, so it’s not something that is flowing from FIM. (There are reasons why it has to be like this to do with AADSync delay.)

Question is: if entity[‘Alumni’] has been changed on Import, will this cause the entity to be part of the $components.InputEntities when the Update script runs on export?

I know if the change comes from FIM via the Adapter it will be in that collection – just want to understand what happens if the change came from the Connector instead.

Congratulations to the UNIFY PG for an outstanding job with IdB5. I haven't had a chance to use it in anger until this weekend just gone, and it was everything I hoped it would be. My goal was to set up a dummy HR connector to create a suitable platform to run my MIMTeam demo on 14th of April, and I was able to reuse some libraries from another project to rapidly build a PowerShell connector to a Mockaroo.com JSON webservice for 1000 random users (with controllable set of reference data).

I am almost finished the demo build and just wanted to say thanks - it's awesome how well this looks and works - particularly given I didn't really know what I was doing when I created the LDAP MA instance and pointed it to IdB5's LDAP service for the first time. Schema discovery meant that I could do refresh/rediscover multiple times as I built up the concepts. Performance is great, and flexibility is outstanding - looking forward to showing this off (just quietly).

I am looking at https://unifysolutions.jira.com/wiki/display/IDB50/Adapter+Overview but I can't find any documentation on how to combine objects from different connectors into the same adapter as I was able to do in IdB4 using a composite adapter. I was always under the impression that the composite adapter idea was being obsoleted but that it was being replaced with another approach which would accommodate this requirement. I now wish to add a "state" object class in my existing "HR Person" adapter. Can I please have a pointer as to how to do this in IdB5?

The following error was reported from a FIM import:

Handling of LDAP search request from user hrma on connection 127.0.0.1:51554 targeting OU=HR,DC=IdentityBroker with a scope of WholeSubtree failed with error "An unrecognized critical control was supplied.". Duration: 00:00:00.

From the error log:

20160403,23:58:20,UNIFY Identity Broker,LDAP engine,Error,"Handling of LDAP search request.

Going by the frequency of the error I believe that it is from the Event Broker agent:

A vanilla Identity Broker v5.0.4 x64 installation is reporting the following alert on the dashboard after startup (Windows 2012 platform):

Configuration does not uniquely identify a certificate. Found 2 certificates.

A vanilla IdB 5.0.4 installation is reporting the following exception on the dashboard after service startup:

The LDAP endpoint failed to startup: An attempt was made to access a socket in a way forbidden by its access permissions

Full error message as follows from the log:

20160401,02:16:10,UNIFY Identity Broker,Logging Engine,Information,Log file started.,Minimal

At DET I have run import all on 4 connectors, bringing in 993 k users, 963 k users, 13 k users and 150 organisations. Part of the check to see that everything had worked is to check LDAP endpoint. One of my containers is missing - the connector import was successful but in the log I see error messages about failing to reflect:

Request to reflect change entities of the adapter.
Request to reflect change entities of the CAMSGeneric (30914957-d066-4f84-97e7-5c29d652d120) adapter errored with message: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.. Duration: 00:16:40.1628000
Error details:
System.Data.SqlClient.SqlException (0x80131904): Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) ...

Any ideas on how to get the connector entities to flow through to the adapter?

I tried clearing the connector to see if an import all might give it the necessary kick, but the clear connector option gives me the warning but does nothing if I select OK - i.e. my connector is unclearable.

Working solution with IDB 5.0.3. Installed 5.0.4 and the custom connector for CAMS failed with:

Change detection engine import all items for connector CAMS User failed with reason Method not found: 'Void Unify.Product.IdentityBroker.DirectEntityFieldsToFieldListConverter..ctor()'..

Richard Green has modified his connector

From Identity Broker 5 web console, the about link presents incomplete version information (missing the major version)