QBWC1048: QuickBooks Web Connector could not verify the web application server certificate (QuickBooks POS 19.0 + QuickBooks Web Connector 2.1.0.30) - quickbooks

I am trying to sync my OpenCart inventory with a QuickBooks POS module via the QuickBooks Web Connector. The documentation says to only use Web Connector version 2.1.0.30 for QB POS. I install the Web Connector on the computer running QB POS 19.0. When I try to add an application I get an immediate QBWC1048 error. Here is the full log output with certain redactions:
20211010.14:08:00 UTC : QWCReader.ParseQWC() : Contents of QWC file: -
<QBWCXML>
<AppName>OpenCart + QBPOS</AppName>
<AppID>id</AppID>
<CertURL>https://fitsfashions.com</CertURL>
<AppURL>https://fitsfashions.com/index.php?route=account/qbposwc</AppURL>
<AppDescription>OpenCart + QBPOS</AppDescription>
<AppSupport>https://fitsfashions.com/index.php?route=information/contact</AppSupport>
<UserName>username</UserName>
<OwnerID>{a60d1e19-bfbb-5b94-e1a8-a34570dc1ed9}</OwnerID>
<FileID>{081bcf7f-6f6a-70c4-0935-cd28bfc05603}</FileID>
<QBType>QBPOS</QBType>
<Notify>false</Notify>
<Scheduler>
<RunEveryNMinutes>5</RunEveryNMinutes>
</Scheduler>
<IsReadOnly>false</IsReadOnly>
</QBWCXML>
20211010.14:08:00 UTC : QBWebConnector.WebServiceManager.ReadQWC(QWCReader QWC) : Parsing application configuration xml file to load its content to variables
20211010.14:08:00 UTC : : QBWC1048: QuickBooks Web Connector could not verify the web application server certificate.
Certificate URL: https://fitsfashions.comStackTrace:
at System.Net.HttpWebRequest.GetResponse()
at QBWebConnector.QWCReader.CheckCertURL()
Message (description of the exception):
The request was aborted: Could not create SSL/TLS secure channel.
Source (name of application or object that caused the exception):
System
TargetSite (method that threw the exception):
System.Net.WebResponse GetResponse()
InnerException:
20211010.14:08:01 UTC : QBWebConnector.WebServiceManager.ReadQWC(QWCReader QWC) : QBWC1048: QuickBooks Web Connector could not verify the web application server certificate.
QBWC1051: The new application was not added
As you can see, I've tried adding the CertURL option with no luck. I also get the same error while running the troubleshooter .qwc file from https://test.developer.intuit.com/QBWC/TroubleshootQBWC/index.aspx. I've looked all over the internet and put in help tickets but somehow no one seems to have a working solution other than the CertURL thing. The website uses a valid cPanel v3 certificate. Please advise.

According to Intuit's documentation ( https://developer.intuit.com/app/developer/qbdesktop/docs/get-started/get-started-with-quickbooks-web-connector ) Web Connector version 2.1.0.30 supports these TLS versions:
support up to TLS 1.0
But your web server doesn't support that old version of TLS:
SSL v2 not offered
SSL v3 not offered
TLS 1.0 not offered
TLS 1.1 is not offered
TLS 1.2 offered
TLS 1.3 offered with final
This is good, because TLS 1.0 is insecure, and should not be used.
You probably want to upgrade to a newer version of the Web Connector, which supports newer versions of TLS:
https://developer.intuit.com/app/developer/qbdesktop/docs/get-started/get-started-with-quickbooks-web-connector#download-and-install-the-quickbooks-web-connector

Related

TLS / SSL implementation for Desktop applications developed using Delphi

I have a desktop client/server application. Both client and server are developed using Delphi 10.2. Application server has been deployed as a Windows service.
My requirement is to implement TLS/SSL to secure the communication between client and server. For this I have used Indy with TIdServerIOHandlerSSLOpenSSL on the server side and TIdSSLIOHandlerSocketOpenSSL on the client side.
For testing purposes, I have used self-signed certificates.
During testing of this setup , I had to setup OpenSSL on each client workstation. Also, I copied libeay32.dll and ssleay32.dll to the system32 folder.
So part of the problem is:
Could this configuration of client workstations be avoided? My understanding with TLS/SSL is that it is server which needs to be configured to enable TLS/SSL.
Since my testing is based on self signed-certificates, I did not install any certificate on client machine. What is the role of certificates for the client machine?

ASP.net MVC 5 TLS 1.2 (chrome warning about TLS 1.0 deprecated)

after deploying an asp.net mvc5 website to a shared hosting (plesk panel) with let's encrypt ssl I see this warning in the chrome console:
The connection used to load resources from https://example.com used TLS 1.0 or TLS 1.1, which are deprecated and will be disabled in the future. Once disabled, users will be prevented from loading these resources. The server should enable TLS 1.2 or later. See https://www.chromestatus.com/feature/5654791610957824 for more information.
is this something that can be fixed in the code of the application, or is it server configuration ?
Copied from comment with some additional info.
The message from Chrome is clear enough,
Chrome attempts to use TLS 1.2 for security (TLS 1.0 and 1.1 are not considered secure).
The server side does not support TLS 1.2 handshakes as Chrome detects.
Therefore, only the server administrators (or service providers ISP) can diagnose and fix such issues.

Trusted Certificate fails after upgrade from 4.6.1 to 4.7.2

After upgrading a service written in F# from 4.6.1 to 4.7.2 i startet getting a classic SSL/TLS error "The request was aborted: Could not create SSL/TLS secure channel".
TLS 1.2 is enabled on all servers.
I verified with Fiddler that the old version and the new version of the application both uses TLS 1.2 as they should and have done for a long time.
The requests appears to be identical.
The service runs as a Network Service, however i get the same error if i run it as admin.
The certificate is selfsigned and placed in Trusted Root Certification Auth.
The certificate is only used to internal https between our services.
If I add the certificate to Personal certificates in certmgr the error disappears and the service works!
From my view it is as if after upgrading to 4.7.2 the Trusted Ca certificates are "ignored".
Adding the certificate to Personal when its placed in Trusted Certificates is not a solution.
I havent been able to identify the change which somehow must have been introduced in 4.7.2.
What am i missing?

Neo4j Enterprise 3.2 browser does not connect

I am trying to learn Neo4j by using the trial Enterprise version, however the browser is not able to connect. The service is running but when I try to log in via browser http://localhost:7474/browser/ the error is:
N/A: WebSocket connection failure. Due to security constraints in your
web browser, the reason for the failure is not available to this Neo4j
Driver. Please use your browsers development console to determine the
root cause of the failure. Common reasons include the database being
unavailable, using the wrong connection URL or temporary network
problems. If you have enabled encryption, ensure your browser is
configured to trust the certificate Neo4j is configured to use.
WebSocket readyState is: 3
In the console the error is:
WebSocket is already in CLOSING or CLOSED state.
I am using Chrome and the neo4j.conf is:
# Bolt connector
dbms.connector.bolt.enabled=true
#dbms.connector.bolt.tls_level=OPTIONAL
dbms.connector.bolt.listen_address=:7687
# HTTP Connector. There must be exactly one HTTP connector.
dbms.connector.http.enabled=true
#dbms.connector.http.listen_address=:7474
# HTTPS Connector. There can be zero or one HTTPS connectors.
dbms.connector.https.enabled=true
#dbms.connector.https.listen_address=:7473
I understand from this issue the 3.2 version only allows bolt and I tried playing with the conf but so far no luck. Is there a way to get the local connection going with bolt?
Thank you in advance, Paola

To connect with AWS IoT broker in iOS

We are developing an application which needs to consume AWS IoT service based on a MQTT protocol deviation. We are currently facing issues to get connected with MQTT broker provided by AWS IoT cloud server.
Following is the environment:
iOS Version: 8.0 / 9.0
Programming language: Swift
Library for MQTT: Moscapsule
Steps followed:
Set initial config clientid, host, port
Set client certificate with private key, providing .pem file path (e.g. cert.pem, privateKey.pem)
Set server certificate which is root certificate .pem file path (e.g. rootCA.pem)
Set tls opts with tsl_insecure: false, cert_reqs: SSL_VERIFY_PEER, tls version: tlsv1.2, ciphers: nil
Problems faced:
When trying to connect to server/broker gives error “unable to create TLS_Context”.
With setting tls cert_reqs: SSL_VERIFY_NONE, gives connection status success with subcribe and publish sucess, but doesn’t reflect on server or broker.
Any help in this context is highly appreciable.
The AWS SDK for iOS already supports connecting to AWS IoT over MQTT. You can see an example Swift program which transfers data to and from AWS IoT over MQTT using certificate-based authentication here. If you'd like to use a different MQTT client and just need to know how to set it up, you might start with the AWS SDK for iOS, and then have a look at the code involved in setting up the TLS connection.
Thanks for using AWS IoT.

Resources