We are testing a BlackBerry app that accesses a secure RESTful service.
One of our customers is getting an "Access Denied: Insecure SSL Request" error when trying to access our web service. The customer device is running OS6. We have not been able to reproduce this with an OS6 simulator. The cert is installed on the simulator that matches his device.
We have seen similar cert problems with OS5 devices and simulators. We are using a Root Level Certificate (Thawte Primary CA) that is not installed on BlackBerry OS5. We have been able to solve similar problems on the OS5 devices by manually installing the certificate.
The manual cert install fix works for accessing the service from the OS6 devices' browser, but we get a "Access Denied: Insecure SSL Request" error when trying a https operation from our app. We are not able to reproduce this on any of our devices.
Questions:
Does the "Access Denied: Insecure SSL Request" error indicate the customer's device isusing the BlackBerry Enterprise Server? All google results for this error indicate the BES.
This cert has a wildcard that points to our many sub-domains. Could switching to a cert that explicitly points to the problem domain solve this? We recently changed our certs, but they work fine on iOS, Android, IE, FireFox & Chrome.
Any there any code changes we can make to fix this? We are creating the connection using the HttpsConnection. We are developing using the Java 5.0 libaray.
What other steps would you recommend for trying to track down this problem?
Related
Need help with implementing Auth0 with Ionic/React. I've followed this documentation, but have not had any luck with an ios simulator.
http works fine when opening the app in the browser, but if I try and run an ios simulator, it complains that "auth0-spa-js must run on a secure origin.".
I've tried adding the simulators host and port numbers to the allowed web origins and callback urls in the Auth0 dashboard. I've tried adding a ssl cert from charles and I've tried...
ionic cap run ios -l --external --https
which starts a server running on https but the ios simulator returns "about:blank" in the developer tools.
Has anyone had any luck with getting Auth0 to work in a simulator?
Im using nodejs to host some images that my website uses. It works perfectly on newer versions of safari, chrome, and firefox. But for some people using old versions of safari, people with old ios devices, cannot use the website, because the images will not load due to an ssl error.
This is what appears in the console with older versions of safari.
Failed to load resource: An SSL error has occurred and a secure connection to the server cannot be made.
this is the website: https://nindoa.mx
My nodejs server uses https and has an AWS certificate using cloudfront.
The error most probably is occurring due to mismatch in TLS versions supported by the device & Cloudfront.
Older devices works on TLS v1.1 or later, while the latest one on TLS v1.2 or newer.
Make sure while creating the Cloudfront cdn you have selected the correct configuration required. You need to identify the TLS supported by the model to debug the issue deeply.
https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/secure-connections-supported-viewer-protocols-ciphers.html
How can I fix this on iOS using Swift? When I'm making a server request I get the following error:
The certificate for this server is invalid. You might be connecting to a server that is pretending to be “...” which could put your confidential information at risk.
You just need to install the certificates on the iOS simulators
From Charles Documentation:
Quit your iOS Simulator. Launch Charles and go to the Help menu.
Choose the "SSL Proxying > Install Charles Root Certificate in iOS
Simulators" item. This will install your Charles Root Certificate into
all of your iOS Simulators. Now when you start the iOS Simulator, you
should be able to access SSL websites with Charles using SSL Proxyin
You are most probably trying to connect to server with self-signed ssl certificate. iOS does not like it.
Take a look at this post as an example: Swift SSL error with self signed certificate.
Other possible issue is a proxy configuration with something like Charles behind it.
More details will maybe help to identify the root of the issue...
I cannot get the "Over The Air" installation of iOS apps to work using the latest version of macOS (10.12.5) and Xcode Server (5.3.1). I can create Xcode Bots and the integrate without any issue, but it always fails with "cannot connect to server.local" when trying to install the app from any device.
The "Xcode Server OTA Installation" profile is installed.
I can download the archive and product using Safari on the Mac without a problem.
In summary, everything work but the OTA installation always fails.
Tried on two different Macs already, also with a complete clean installation of macOS before.
Versions: macOS 10.12.5, Xcode 8.3.2 and Server 5.3.1
I found several old reports of this problem but all the workarounds didn't seem to help.
Same problem on Xcode 9 beta 1 with the now built-in Xcode server.
For iOS 10.3 and later, a reason why fails, in some cases, with "Cannot connect to *.local" is that self-signed certificate shall be trusted manually in Settings on test devices (eg. iPhone).
Steps as follow:
Install self-signed certificate(s) from Xcode server's bots page on your iPhone;
Go to iPhone's Settings->General->About->Certificate Trust Settings;
Find your server's self-signed certificate(s) under section ENABLE FULL TRUST FOR ROOT CERTIFICATES, and turn the switch ON;
Visit bots page on Xcode Server, click install.
My SSL certificate had expired thats why happened to me. Make sure you add that to the list of things to check. Once I renewed that it started working again.
I had this issue on Xcode9 GM. I have installed profile on the Xcode server page and trust the profile. Is this a signing error? I use "export: installable product" for server bot.
I have a certificate problem when install app with OTA deployment site in intranet.
The OTA site is not SSL, it works fine with iOS 6.x, but it just failed to install in iOS 8 with certificate problem.
We don't use MDM for deployment and I have tried to use self-signed certificate to build a SSL OTA site, but it still failed.
I want to ask if there is any advise to fix this problem?
Thank you very much!
You have to use a real SSL certificate with new iOS versions. Using self-made certificate might work if you install it on the devices, but I haven't tried this.
Note that the actual ipa doesn't have to be on a SSL secured site, only the plist file. And you could use 3rd party file storing services to host that file and have the ipa on another server.