Invalid signature file digest for Manifest main attributes

Issue on Connector Server while starting.

C:\connector_server_java-1.5.0\bin>ConnectorServer.bat /run

Exception in thread "main" java.lang.SecurityException: Invalid signature file digest for Manifest main attributes

at sun.security.util.SignatureFileVerifier.processImpl(SignatureFileVerifier.java:317)

at sun.security.util.SignatureFileVerifier.process(SignatureFileVerifier.java:259)

at java.util.jar.JarVerifier.processEntry(JarVerifier.java:323)

at java.util.jar.JarVerifier.update(JarVerifier.java:234)

at java.util.jar.JarInputStream.read(JarInputStream.java:212)

at java.util.zip.ZipInputStream.closeEntry(ZipInputStream.java:140)

at java.util.zip.ZipInputStream.getNextEntry(ZipInputStream.java:118)

at java.util.jar.JarInputStream.getNextEntry(JarInputStream.java:142)

at java.util.jar.JarInputStream.getNextJarEntry(JarInputStream.java:179)

at org.identityconnectors.framework.impl.api.local.LocalConnectorInfoManagerImpl.processURL(LocalConnectorInfoManagerImpl.java:199)

at org.identityconnectors.framework.impl.api.local.LocalConnectorInfoManagerImpl.expandBundles(LocalConnectorInfoManagerImpl.java:91)

at org.identityconnectors.framework.impl.api.local.LocalConnectorInfoManagerImpl.<init>(LocalConnectorInfoManagerImpl.java:72)

at org.identityconnectors.framework.impl.api.ConnectorInfoManagerFactoryImpl.getLocalManager(ConnectorInfoManagerFactoryImpl.java:81)

at org.identityconnectors.framework.server.impl.ConnectorServerImpl.start(ConnectorServerImpl.java:68)

at org.identityconnectors.framework.server.Main.run(Main.java:206)

Solution:

1) Check the folder structure of your connector server

2) Remove any other jars from bundles folder and keep only bundle jar in it.

In my case, somebody kept supporting jars as well in the same folder along with my bundle jar(org.identityconnectors.dbum-12.3.0.jar)

SQLServerException:This driver is not configured for integrated authentication

Seeing Error while provisioning to MSSQL Connector:

[ERROR] [] [ORACLE.IAM.CONNECTORS.ICFCOMMON.RECON.LOOKUPRECONTASK] [tid: OIMQuartzScheduler_Worker-4] [userId: oiminternal] [ecid: 73ac5db7-f9df-4987-82d4-b6bf434d2467-000000a6,0:296] [APP: oim] [partition-name: DOMAIN] [tenant-name: GLOBAL] oracle.iam.connectors.icfcommon.recon.LookupReconTask : execute : Error during execution[[

java.lang.RuntimeException: com.microsoft.sqlserver.jdbc.SQLServerException: This driver is not configured for integrated authentication. ClientConnectionId:0edda621-37af-41bb-89d8-3542d00f387b

Solution:

1) mssql-jdbc-<latest_version>.jar is missing

Note: check the jdk version for your target and oim.
If you are 11g then the jar must be compatible with jdk1.7 but if you are on 12c then it should be working be jdk1.8. same way check the jdk versions on your connector server and target database.

2) Register this jar on oim server using UploadJars utility

3) Give the reference of this jar in setDomainEnv.sh

POST_CLASSPATH="/opt/oracle/apps/OIM_Middleware/oracle_common/modules/thirdparty/mssql-jdbc-9.4.0.jre8.jar${CLASSPATHSEP}${POST_CLASSPATH}"

export POST_CLASSPATH

4) You need to give the below jars reference additionally.

POST_CLASSPATH="/opt/oracle/apps/OIM_Middleware/idm/server/ThirdParty/ojdbc8.jar${CLASSPATHSEP}${POST_CLASSPATH}"

export POST_CLASSPATH

POST_CLASSPATH="/opt/oracle/apps/OIM_Middleware/oracle_common/lib/ons.jar${CLASSPATHSEP}${POST_CLASSPATH}"

export POST_CLASSPATH