We have an issue with SSL since a few days ago.
Our APIs reside at amazon, and the app is calling the API via HTTPS.
For months it has been good, but since a few days we started getting:
An SSL error has occurred and a secure connection to the server cannot
be made.
Amazon says its nothing on their side. But we can't pinpoint on the issue, as this is happens sporadically and random countries, ios versions and models...
How can we understand where the problem is?
Thank you
Related
I have a .NET 4.6, MVC 5 web application making a REST call to another service using OAUTH.
The web application is deployed on Azure's App Service.
Most of the time, it works perfectly.
Both my App and the Target API use SSL and I have tested both on SSLabs.com, and both come out at A and supporting TLS1.2
However occasionally the the API link seems to get "knocked out" and all calls produce the error:
The request was aborted: Could not create SSL/TLS secure channel.
This is logged in our Elmah log.
The only way to resolve this at present is to restart the Azure App Service.
I have researched this ie
The request was aborted: Could not create SSL/TLS secure channel for HttpWebRequest
Only one App Service (live) seems affected. This may be because it is used more and trigger the problem sooner. The QA one seems fine. QA is used fairly heavily due to testing activities. Not sure if this is circumstantial
I have now hit a dead end. Key clue may be in having to restart the App Service to get it working again.
Any pointers appreciated.
Many thanks.
The issue is that users trying to connect to a SharePoint 2016 site using https will be continually prompting for credentials when browsing using an Apple iOS devices (iPhone, iPad, etc).
We have spoken to Microsoft about this issue and appears to be a known problem and came back to us with the following response.
This issue occurs as the SharePoint Authentication is not compatible
with the IOS
As of now this issue has been reported but the change is required from
the Apple end, such that the IOS accepts the SharePoint
Authentication.
They recommended a few work arounds, but it appears that there are a lot of cases with similar problems, so I was just wondering what work around others are using, until a fix is put in place.
Using Http url for SharePoint
Using a Web Application Proxy for SharePoint https://blogs.msdn.microsoft.com/sambetts/2015/07/01/sharepoint-server-and-web-application-proxy-continued/
The current work around for me is to use a web proxy but this pain as it needs to be updated on each device for each connection.
I had exactly the same issue with HTTPS and SharePoint 2016.
The issue was solved by disabling HTTP/2 for IIS 10. I had to create two registry keys: under HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters
EnableHttp2Tls REG_DWORD 0
EnableHttp2Cleartext REG_DWORD 0
Update
This should only take effect after you restart the server.
I have been developing iOS for years but this is my first time building a backend for an app, so SSL subject matter isn't a strong point for me.
I have installed a SSL certificate on my IIS 8.0 (Server 2012). I have confirmed that the https endpoint is functioning properly.
My question: Is there anything I have to do in my iOS application (using RestKit 0.2 for server communication) other than change the endpoint from http to https? I'm not sure when I consider the traffic going to the server to be "secure". Bit of a noob question I know but, I don't want to miss something simple on the iOS side and think everything is secure when it is not.
Thanks for any help.
I am currently developing a Ruby/Rails app that will be used in-house as a sort of Enterprise application to support our business.
Our company uses Quickbooks Online to do almost all of our accounting, most importantly for invoicing.
I am looking for a way to automatically generate invoices from our Rails app into Quickbooks, as well as be able to pull customer balances and some other "basic" information into the Rails app to display on a customer information screen.
I have done a lot of research on the topic, and have yet to find an acceptable solution to what we're trying to accomplish.
Quickbooks Web Connector - Not applicable since are not running Quickbooks Pro
Intuit Anywhere app - The app we are using is certainly not a SaaS App, as it is specifically designed for our business, and the only Quickbooks file/account it will ever see is our own
Quickbooks Online/qbXML Gateway application - This seems to be the best fit
So I have spent considerable time with Keith Palmer's Consolibytes wiki, and Intuit's Official Documentation (which is great to get started, but doesn't really provide much help for the details), and have been unable to even link my application to quickbooks using the https://qbo.intuit.com/redir/addsdkapp?appid=YOUR-ID-HERE&appreferer=&appdata=1 link.
My server does have a GoDaddy generated SSL certificate, and I have visited the connection callback URL and have confirmed that everything is in working order there. However, I keep getting a "Failed to notify third party application about this connection" error. There is no evidence of a request from QB to my server in any of my logs.
So what I'm getting at here is this:
Is what I'm trying to do possible and/or practical?
Am I going the right way about it?
I'd really love to find someone out there who has done something like this before and maybe shed some light on the whole process.
Thanks!
So what I'm getting at here is this: Is what I'm trying to do possible and/or practical?
Yes.
Am I going the right way about it?
Almost. :-)
From what you posted:
My server does have a GoDaddy generated SSL certificate, and I have visited the connection callback URL and have confirmed that everything is in working order there.
It sounds like you registered in HOSTED mode.
Unfortunately, the Intuit servers don't consider GoDaddy certificates valid, and thus won't be able to HTTP POST your connection ticket to those servers. That's why you're seeing this:
Failed to notify third party application about this connection
Additionally, I believe they do reverse DNS checks, which will most likely fail because GoDaddy generally doesn't set up rDNS entries.
The solution is:
Do not register in HOSTED mode
Instead, register in DESKTOP mode.
Once you've registered, use this URL to register get your connection ticket:
https://login.quickbooks.com/j/qbn/sdkapp/confirm?appid=YOUR-APPLICATION-ID-HERE&serviceid=2004&appdata=1
(make sure to plug your actual application ID into the URL)
Instead of Intuit HTTP POSTing the connection ticket to you, the connection ticket will be displayed and you can copy/paste it. From there on in, it's as simple as HTTP POSTing additional HTTP requests to Intuit's servers.
Sample XML requests can be found on our QuickBooks integration wiki - make sure you use the DESKTOP mode examples.
Hope that helps clear things up!
as of about 3 hours ago every call to the Doclist API using 2-legged OAuth started failing with "500 Internal Error" messages.
We have verified this from multiple systems (App Engine and local apps) using different libraries, and across domains in Asia, US and Europe.
The problem does NOT occur if normal user authentication is used - only 2LO is affected.
Unfortunately this issue affects thousands of students using our tools.
http://code.google.com/a/google.com/p/apps-api-issues/issues/detail?id=3233&thanks=3233&ts=1347419864
Jan
This is tracked at http://code.google.com/a/google.com/p/apps-api-issues/issues/detail?id=3233 and the fix should be live very soon.
UPDATE: everything is now back to normal