[midPoint] The connector was not found error

[Florin. Stingaciu]

Turns out it was a permission error writing to /tmp/ due to an issue with
the container tomcat7 user. I didn't know midPoint expanded there, but I
guess it makes sense. Please ignore.

Thanks,
-F

On Fri, Oct 21, 2016 at 11:33 AM, Florin. Stingaciu <fstingaciu at mirantis.com
> wrote:

> Hey all,
>
> I'm trying to move midPoint into a Docker container and upon importing my
> resource, I get the following error:
>
> Error resolving connector reference in resource:2daa0493-e506-46b6-83b5-a0133ee9dc99(Corporate
> Active Directory): Error creating connector instace: The classes (JAR) of
> connector: ICF com.evolveum.polygon.connector.ldap.ad.AdLdapConnector
> v1.4.2.17 (OID:859ee3d5-b885-411b-9e73-79ff631a71a6) were not found by
> the ICF framework; bundle=com.evolveum.polygon.connector-ldap connector
> type=com.evolveum.polygon.connector.ldap.ad.AdLdapConnector,
> version=1.4.2.17
>
> I've double checked my configuration from prod to the config here and I
> see no difference. I can see the jar file in: /var/lib/tomcat7/webapps/
> midpoint/WEB-INF/lib/connector-ldap-1.4.2.17.jar
>
> I can also see the connectors in the Repo. And in my connector
> configuration on the resource, the OID resolves to the connector in the
> Repo.
>
> I'm sure it's something minuscule but I can't seem to figure out what
> exactly.
>
> Thanks,
> -F
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20161021/d99e6f66/attachment.htm>