<div dir="ltr">Hi Ivan -<div><br></div><div>Apologies for the late reply.</div><div><br></div><div>Let me tell you the whole story :) So when I was trying to get the AD resource to work on midpoint, I realised that there were newer version of both the .NET connector server, and the connector itself (I landed up on Oracle's site when I was investigating some issue and found everything there). </div>
<div><br></div><div>The connector server version is :</div><div><div>Connector Server 11.1.2.1.0 - July 2, 2013<br></div></div><div>And the AD connector : 1.1.0.6380</div><div><br></div><div>So after the connector "discovery" step (after I imported my connector host configuration), I realised that now the list of connectors had TWO connectors - the old one (I cannot remember the version exactly) and a definition for the new one (1.1.0.6380). It seems that both of these definitions have the same connector type :</div>
<div><br></div><div>Org.IdentityConnectors.ActiveDirectory.ActiveDirectoryConnector<br></div><div><br></div><div>So now, when I imported the AD resource, there was an error - it seems that the query inside <connectorRef>, the <q:equal> query, returns two matches (since I have both the definitions).</div>
<div><br></div><div>So just to test this, I went to the object list and edited the Connector object (the new one) and just modified the connector type string a little. And then it worked.</div><div><br></div><div>Subsequently I manually deleted the old connector definition so there are no conflicts.</div>
<div><br></div><div>I hope this clarifies your question..?</div><div><br></div><div>-deepak</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 31 October 2013 08:14, Ivan Noris <span dir="ltr"><<a href="mailto:ivan.noris@evolveum.com" target="_blank">ivan.noris@evolveum.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
Hi Deepak,<br>
<br>
can you please clarify why you did have to change the connectorType?<br>
<br>
After you did the Connector Discovery, was the connector object
created in midPoint? In my case, the connector object contains:<br>
<br>
<connectorType>Org.IdentityConnectors.ActiveDirectory.ActiveDirectoryConnector</connectorType><br>
<br>
After that, you imported your AD resource, (with original connector
reference) - didn't that work? Was this the reason why you had to
update the connector type?<br>
<br>
AFAIK you never have to update anything in the connector object
itself (or I've never had to).<br>
<br>
Regards,<br>
Ivan<div><div class="h5"><br>
<br>
<div>On 10/30/2013 11:20 AM, Deepak
Natarajan wrote:<br>
</div>
</div></div><blockquote type="cite"><div><div class="h5">
<div><br>
</div>
<div>Hi - </div>
<div><br>
</div>
<div>I'm experimenting with updating
the .NET connector server and the connector itself (for midpoint
2.2). I don't know if I should be doing this, but what the heck
:)</div>
<div><br>
</div>
<div>I obtained the "latest" .NET
connector server from Oracle and installed it on Windows Server
2008 R2. And also the latest active directory connector.</div>
<div><br>
</div>
<div>On midpoint I configured the
connector host - no errors here, the discovery was successful. </div>
<div><br>
</div>
<div>In the list of connector objects,
I see a new connector now :</div>
<div>ICF
Org.IdentityConnectors.ActiveDirectory.ActiveDirectoryConnector
v1.1.0.6380 @APOS/AD Connector Server (Vejle)</div>
<div><br>
</div>
<div>[ </div>
<div>I had to adjust the schema for
this and change the ConnectorType to</div>
<div><connectorType>Org.IdentityConnectors.ActiveDirectory.ActiveDirectoryConnector.1.1</connectorType></div>
<div>to avoid an error when importing
the resource again]</div>
<div><br>
</div>
<div>When I try to test my new AD
resource, I get the following error below :</div>
<div><br>
</div>
<div> Error resolving connector
reference in <a>resource:70a9c241-4c8e-4d72-b3f2-79015e476299(APOS</a>
AD (Vejle) Resource): Error creating connector instace: The
classes (JAR) of <b>connector: ICF
Org.IdentityConnectors.ActiveDirectory.ActiveDirectoryConnector
v1.1.0.6380 @APOS/AD Connector Server (Vejle)
(OID:637e281c-dc20-41f5-8197-b83886ec4319) were not found by
the ICF framework; connector
type=Org.IdentityConnectors.ActiveDirectory.ActiveDirectoryConnector.1.1,
version=1.1.0.6380<br>
Cause:<br>
</b><br>
The classes (JAR) of connector: ICF
Org.IdentityConnectors.ActiveDirectory.ActiveDirectoryConnector
v1.1.0.6380 @APOS/AD Connector Server (Vejle)
(OID:637e281c-dc20-41f5-8197-b83886ec4319) were not found by the
ICF framework; connector
type=Org.IdentityConnectors.ActiveDirectory.ActiveDirectoryConnector.1.1,
version=1.1.0.6380<br>
[ HIDE ERROR STACK ]<br>
<b>com.evolveum.midpoint.util.exception.ObjectNotFoundException:
The classes (JAR) of connector: ICF
Org.IdentityConnectors.ActiveDirectory.ActiveDirectoryConnector
v1.1.0.6380 @APOS/AD Connector Server (Vejle)
(OID:637e281c-dc20-41f5-8197-b83886ec4319) were not found by
the ICF framework; connector </b>type=Org.IdentityConnectors.ActiveDirectory.ActiveDirectoryConnector.1.1,
version=1.1.0.6380<br>
at
com.evolveum.midpoint.provisioning.impl.ConnectorManager.createConfiguredConnectorInstance(ConnectorManager.java:147)<br>
at
com.evolveum.midpoint.provisioning.impl.ConnectorManager.getConfiguredConnectorInstance(ConnectorManager.java:122)<br>
at
com.evolveum.midpoint.provisioning.impl.ResourceManager.getConnectorInstance(ResourceManager.java:803)<br>
at
com.evolveum.midpoint.provisioning.impl.ResourceManager.completeResource(ResourceManager.java:244)<br>
at
com.evolveum.midpoint.provisioning.impl.ResourceManager.putToCache(ResourceManager.java:144)<br>
at
com.evolveum.midpoint.provisioning.impl.ResourceManager.getResource(ResourceManager.java:138)<br>
at
com.evolveum.midpoint.provisioning.impl.ProvisioningServiceImpl.getObject_aroundBody0(ProvisioningServiceImpl.java:189)<br>
at
com.evolveum.midpoint.provisioning.impl.ProvisioningServiceImpl$AjcClosure1.run(ProvisioningServiceImpl.java:1)<br>
</div>
<div><br>
</div>
<div>Does this mean my experiment has
failed? It looks like something in the midpoint core has to
change to accommodate new connector versions?</div>
<div><br>
</div>
<div>Thanks!</div>
<div><br>
</div>
<div>-deepak</div>
<br>
<fieldset></fieldset>
<br>
</div></div><pre>_______________________________________________
midPoint mailing list
<a href="mailto:midPoint@lists.evolveum.com" target="_blank">midPoint@lists.evolveum.com</a>
<a href="http://lists.evolveum.com/mailman/listinfo/midpoint" target="_blank">http://lists.evolveum.com/mailman/listinfo/midpoint</a><span class="HOEnZb"><font color="#888888">
</font></span></pre><span class="HOEnZb"><font color="#888888">
</font></span></blockquote><span class="HOEnZb"><font color="#888888">
<br>
<pre cols="72">--
Ing. Ivan Noris
Consultant
Evolveum, s.r.o
___________________________________________________
"Semper cautus - semper paratus - semper idem Vix."
</pre>
</font></span></div>
<br>_______________________________________________<br>
midPoint mailing list<br>
<a href="mailto:midPoint@lists.evolveum.com">midPoint@lists.evolveum.com</a><br>
<a href="http://lists.evolveum.com/mailman/listinfo/midpoint" target="_blank">http://lists.evolveum.com/mailman/listinfo/midpoint</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div>Trilobyte Systems ApS</div><div>Copenhagen, Denmark</div><div><br></div><div><br></div>
</div>