Usage of ConnId connector API

[Maarten Winkels]

Hello, We're currently developing a new connector with the connid framework. We run into some question on how the conn if connector API is used by Syncope. Implementing and integrating the create method was very simple: We can see account being provisioned to the resource. Question 1: Syncope seems (however) not to use the delete method correctly if the connector doesn't implement the SearchOp interface: First the current data is requested using the search operation and ONLY if this returns a ConnectorObject the delete is executed. If the SearchOp is not implemented or returns NULL, Syncope silently ignores the delete operation. <code location="org.apache.syncope.core.propagation.impl.AbstractPropagationTaskExecutor:287">             // Try to read remote object (user / group) BEFORE any actual operation             beforeObj = getRemoteObject(task, connector, false); </code> <code location="org.apache.syncope.core.propagation.impl.AbstractPropagationTaskExecutor:234">         if (beforeObj == null) {             LOG.debug("{} not found on external resource: ignoring delete", task.getAccountId());         } else {... </code> Can this behaviour be configured? Question 2: The resource assigns it's own id's, based on the location of the account in the tree. The connector returns the created ID as a Uid to Syncope. When deleting the account from Syncope, the assigned Uid is not used, but only the "Syncope-ID" is provided to the connector to delete the account. How should the connector retrieve the assigned ID? Thanks in advance! Maarten Winkels | IWelcome BV Wiersedreef 5-7 3433 ZX Nieuwegein The Netherlands Tel: +31 (0) 30 6592254 Mob. +31 (0) 6 10038878 Email: maarten.wink...@iwelcome.com Website: http://www.iwelcome.com The information in this Internet email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this Internet email by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. When addressed to our clients any opinions or advice contained in this Internet email are subject to the terms and conditions expressed in any applicable governing Everett terms of business or client engagement letter.