I am using swfUpload (Flash control) to upload files to the web site.
This is working great except when the web site uses SSL with client certificate for authentication.
In IE there is no problem, but with Chrome and Firefox the upload fails.
The upload then fails because the POST request with the file data (coming from swfUpload) is rejected because the client certificate is not provided with the post.
I guess this is a Flash Plugin problem since it is working correctly in IE using the same swfUpload.swf...
Anyone familiar with this problem and is there a fix?
Related
We are using AEM as content service and exporting AEM content into mobile application. For example below api will be used in mobile application and Mobile application will build the presentation layer.
/content/we-retail/us/en/products/women/shirts/jcr:content/root/content-tile.model.json
Here I basically want to authenticate AEM API before I serve the json response. In essence, I want to only accept requests from mobile applications. I should the request If anyone else calls AEM.
I am planning to use an SSL client certificate to confirm that the request is valid. I am confused who generates the SSL certificates. Is it something mobile application generates the certification and dispatcher use and add the certification. or the opposite way, AEM to generates the certificate and mobile application use
This is a little unclear. Could someone please explain to me who should create the certification file?
I am currently working on an .NET 5 & SignalR application and in localhost everything seems to be working fine. When I try to deploy it to IIS pre-production Server which doesn't have a SSL certificate configured, pages other than Login are showing the message "This site can’t provide a secure connection". In the login page from the browser console I can see that most of me javascript and css files aren't loaded with the error "Failed to load resource: net::ERR_SSL_PROTOCOL_ERROR". Also from what I can see after user logs in, the request is redirected to Https.
I have removed app.UseHttpsRedirection(); from the Startup and disabled SSL in the Debug properties of the application. That seems to be a wired behavior because I used to deploy applications in .NET CORE before and didn't have these kind of problems. is there any way around this problem, except configuring an SSL certificate?
From the suggestions in server fault, configuring a self-signed certificate provided by IIS itself seems to be the problem solver. Still I don't get why the application was making that https redirection, but anyways in case someone else has this kind of issue.
I'm currently using Google Earth Pro 7.3.0.3830. I'm trying to access our KML feed behind an https link. The web server is using a self-signed cert that has a self-signed user cert associated with it (same CA). On Windows, I have the CA cert in the trusted windows store as well as the user certificate (both show up in chrome and IE). If I use the Google Earth plugin within Chrome, I can create a network link with https and access the feed. If I use the stand alone Google Earth app, I can't access it (red dot on the folder).
If I change the web server to allow http access and change the feed link, it displays fine on the standalone Google Earth app, (but using just http isn't desirable).
I can't figure out how to get Google Earth to use the client certificate to authenticate the https request to the web server. This is an issue for running Google Earth Pro in both Windows 10 and Centos 7.
Thanks in advance.
Please use Google Earth Pro 7.3.1.4507. It has the required ssl fix.
Please refer release notes
https://support.google.com/earth/answer/40901?hl=en
Based on the release notes for 7.3, SSL client certificates aren't supported in Google Earth Pro 7.3. I'm not sure, but the older versions may have support for them which you can download here.
I want to retrieve JSON files from a secure server using WebClient but my Windows Phone 8 doesn't let me as WebCLient throws an exception if it doesn't trust the SSL certificate.
The problem is that it doesn't trust most of them; Internet Explorer shows me a warning, which I can ignore by adding the certificate, but WebClient doesn't let me do that, it just blocks most of SSL sites - for example:
https://google.com
https://www.digicert.com
With HTTP everything works fine; My iPhone and Android apps are working perfectly with the service.
Is there any way to fix this or bypass SSL checking altogether?
Check your phone's time. If the system time/date is way off SSL will break. This is common on all platforms.
It is not possible to bypass SSL checking.
I've some problems with chromecast and self signed ssl certificate. I tried to implement my own receiver and registered my URL on Google Cast Developer Console.
Chromecast sender application trys to start and then i get some errors.
Does anyone knows if chromecast works with self signed certificates?
It won't work with self-signed certs. For development, you can consider using App Engine or Google Drive since both have valid certs.
Update: Google Drive is no longer an option.
You only need to worry about certs if you're app is ready to publish. During development you can work over HTTP. From https://developers.google.com/cast/docs/registration
"Enter a URL that the Google Cast device should request when loading your receiver app. During development the URL can use HTTP but when the app is published it has to use HTTPS. The URL may be for an HTML page or other file type accessible from a web browser. It's okay for your receiver to be on an internal (NAT-registered) IP address, but not on localhost, as it is rarely a top level domain. Although the receiver app must be served over SSL (HTTPS) when published, the content loaded on the receiver app may be served over HTTP.
Although the receiver app must be served over SSL (HTTPS), the content loaded on the receiver app may be served over HTTP."