Information below on the Remote Site's old working certicate, new/renewed failing certificate and exception. No other change on the SF side or Remote Site. --------------------------------------------------------------------- Root certificate IS THE SAME FOR BOTH, the old and new/renewed certificates: CN = VeriSign Class 3 Public Primary Certification Authority - G5 OU = (c) 2006 VeriSign, Inc. - For authorized use only OU = VeriSign Trust Network O = VeriSign, Inc. C = US Thumbprint 4e b6 d5 78 49 9b 1c cf 5f 58 1e ad 56 be 3d 9b 67 44 a5 e5 ---------------------- The above root certificate seems to be the same as in SF Outbound Messaging SSL CA Certificates: https://developer.salesforce.com/page/Outbound_Messaging_SSL_CA_Certificates#verisignclass3g5ca • 105 verisignclass3g5ca Owner: CN=VeriSign Class 3 Public Primary Certification Authority - G5, OU="(c) 2006 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US Issuer: CN=VeriSign Class 3 Public Primary Certification Authority - G5, OU="(c) 2006 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US Serial number: 18dad19e267de8bb4a2158cdcc6b3b4a Valid from: Tue Nov 07 16:00:00 PST 2006 until: Wed Jul 16 16:59:59 PDT 2036 Certificate fingerprints: MD5: CB:17:E4:31:67:3E:E2:09:FE:45:57:93:F3:0A:FA:1C SHA1: 4E:B6:D5:78:49:9B:1C:CF:5F:58:1E:AD:56:BE:3D:9B:67:44:A5:E5 Signature algorithm name: SHA1withRSA Version: 3 --------------------------------------------------------------------- However, the intermediate certificate issuers are different:
Remote Site's old certicate that worked with intermediate issuer: CN = VeriSign Class 3 International Server CA - G3 OU = Terms of use at https://www.verisign.com/rpa (c)10 OU = VeriSign Trust Network O = VeriSign, Inc. C = US
Remote Site's new, renewed certicate that fails with intermediate issuer: CN = Symantec Class 3 Secure Server CA - G4 OU = Symantec Trust Network O = Symantec Corporation C = US --------------------------------------------------------------------- Remote Site's new, renewed certicate exception in SF: Exception: https://... sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
--------------------------------------------------- Ref: http://en.wikipedia.org/wiki/ISO/IEC_8859#Table ASCII Extended ISO-8859-1/ISO-Latin-1 Western European
Information below on the Remote Site's old working certicate, new/renewed failing certificate and exception. No other change on the SF side or Remote Site. --------------------------------------------------------------------- Root certificate IS THE SAME FOR BOTH, the old and new/renewed certificates: CN = VeriSign Class 3 Public Primary Certification Authority - G5 OU = (c) 2006 VeriSign, Inc. - For authorized use only OU = VeriSign Trust Network O = VeriSign, Inc. C = US Thumbprint 4e b6 d5 78 49 9b 1c cf 5f 58 1e ad 56 be 3d 9b 67 44 a5 e5 ---------------------- The above root certificate seems to be the same as in SF Outbound Messaging SSL CA Certificates: https://developer.salesforce.com/page/Outbound_Messaging_SSL_CA_Certificates#verisignclass3g5ca • 105 verisignclass3g5ca Owner: CN=VeriSign Class 3 Public Primary Certification Authority - G5, OU="(c) 2006 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US Issuer: CN=VeriSign Class 3 Public Primary Certification Authority - G5, OU="(c) 2006 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US Serial number: 18dad19e267de8bb4a2158cdcc6b3b4a Valid from: Tue Nov 07 16:00:00 PST 2006 until: Wed Jul 16 16:59:59 PDT 2036 Certificate fingerprints: MD5: CB:17:E4:31:67:3E:E2:09:FE:45:57:93:F3:0A:FA:1C SHA1: 4E:B6:D5:78:49:9B:1C:CF:5F:58:1E:AD:56:BE:3D:9B:67:44:A5:E5 Signature algorithm name: SHA1withRSA Version: 3 --------------------------------------------------------------------- However, the intermediate certificate issuers are different:
Remote Site's old certicate that worked with intermediate issuer: CN = VeriSign Class 3 International Server CA - G3 OU = Terms of use at https://www.verisign.com/rpa (c)10 OU = VeriSign Trust Network O = VeriSign, Inc. C = US
Remote Site's new, renewed certicate that fails with intermediate issuer: CN = Symantec Class 3 Secure Server CA - G4 OU = Symantec Trust Network O = Symantec Corporation C = US --------------------------------------------------------------------- Remote Site's new, renewed certicate exception in SF: Exception: https://... sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
I have had great success in using .net and the associated API Enterprise generated WSDL and Web Reference for about a year. I've also used the API in the Sandbox. I hadn't made a change to the Sandbox or the Production for a couple of months. Today I did the following in Firefox (I have had more success generating and downloading the WSDL in Firefox)
- Went to Settings/Develop/API/Generate Enterprise WSDL and clicked the GENERATE button to the right of "Generate Enterprise WSDL" - The result in Firefox was not the normal formatted XML that I had seen in the past (perhaps the update to Firefox did this) What appeared was what looked like one big paragraph of sentences (no xml tags) - I right clicked in the white area of the page and "saved as" test.wsdl - When I opened test.wsdl, it looked like it alwas does...properly formed XML
Next in VS, I changed the Web Reference property to the Test.wsdl file name and Updated my Web Reference
====================================== Now the issue (finaly) ======================================
When I try to create an instance of SforceService like the code below:
SforceService sfService = new SforceService();
I get the following exception:
2014-09-11 16:35:30.000 Warning SalesforceClient.Connect Exception.Exception.Name InvalidOperationException 2014-09-11 16:35:30.000 Warning SalesforceClient.Connect Exception.Exception.Message Unable to generate a temporary class (result=1). 2014-09-11 16:35:30.000 Warning SalesforceClient.Connect Exception.Exception.Message error CS0030: Cannot convert type 'Mozenda.Business.Salesforce.ListViewRecordColumn[]' to 'Mozenda.Business.Salesforce.ListViewRecordColumn' 2014-09-11 16:35:30.000 Warning SalesforceClient.Connect Exception.Exception.Message error CS0030: Cannot convert type 'Mozenda.Business.Salesforce.ListViewRecordColumn[]' to 'Mozenda.Business.Salesforce.ListViewRecordColumn' 2014-09-11 16:35:30.000 Warning SalesforceClient.Connect Exception.Exception.Message error CS0029: Cannot implicitly convert type 'Mozenda.Business.Salesforce.ListViewRecordColumn' to 'Mozenda.Business.Salesforce.ListViewRecordColumn[]' 2014-09-11 16:35:30.000 Warning SalesforceClient.Connect Exception.Exception.Message error CS0029: Cannot implicitly convert type 'Mozenda.Business.Salesforce.ListViewRecordColumn' to 'Mozenda.Business.Salesforce.ListViewRecordColumn[]' 2014-09-11 16:35:30.000 Warning SalesforceClient.Connect Exception.Exception.Source System.Xml 2014-09-11 16:35:30.000 Warning SalesforceClient.Connect Exception.Exception.StackTrace at System.Xml.Serialization.Compiler.Compile(Assembly parent, String ns, XmlSerializerCompilerParameters xmlParameters, Evidence evidence) 2014-09-11 16:35:30.000 Warning SalesforceClient.Connect Exception.Exception.StackTrace at System.Xml.Serialization.TempAssembly.GenerateAssembly(XmlMapping[] xmlMappings, Type[] types, String defaultNamespace, Evidence evidence, XmlSerializerCompilerParameters parameters, Assembly assembly, Hashtable assemblies) 2014-09-11 16:35:30.000 Warning SalesforceClient.Connect Exception.Exception.StackTrace at System.Xml.Serialization.TempAssembly..ctor(XmlMapping[] xmlMappings, Type[] types, String defaultNamespace, String location, Evidence evidence) 2014-09-11 16:35:30.000 Warning SalesforceClient.Connect Exception.Exception.StackTrace at System.Xml.Serialization.XmlSerializer.GetSerializersFromCache(XmlMapping[] mappings, Type type) 2014-09-11 16:35:30.000 Warning SalesforceClient.Connect Exception.Exception.StackTrace at System.Xml.Serialization.XmlSerializer.FromMappings(XmlMapping[] mappings, Type type) 2014-09-11 16:35:30.000 Warning SalesforceClient.Connect Exception.Exception.StackTrace at System.Web.Services.Protocols.SoapClientType..ctor(Type type) 2014-09-11 16:35:30.000 Warning SalesforceClient.Connect Exception.Exception.StackTrace at System.Web.Services.Protocols.SoapHttpClientProtocol..ctor() 2014-09-11 16:35:30.000 Warning SalesforceClient.Connect Exception.Exception.StackTrace at Mozenda.Business.Salesforce.SforceService..ctor() 2014-09-11 16:35:30.000 Warning SalesforceClient.Connect Exception.Exception.StackTrace at Mozenda.Business.SalesforceClient.SalesForceClient.Connect()
There is alot if information about "Unable to generate a temporary class (result=1)" doing a Google search, but nothing seems to apply.
- Has Salesforce changed how the Enterprise WSDL is created?
