Disclaimer: I'm an Air newbie (about 20 minutes in to this experiment).
I have a demo application using Adobe Air that accesses my own SSL web service that uses a self-signed certificate. In .NET clients, I can explicitly handle (and ignore) certificate warnings and suppress them via the ServicePointManager.ServerCertificateValidationCallback. Does anything similar exist in Air? I've examined the URLRequest and URLLoader classes but haven't found anything.
If you are using Windows XP install the untrusted or unknown certificate in your Trusted Root Certificate Authorities. You can install the certificate from Internet Explorer while accessing your site.
There is a registered bug On Vista and Windows 7. The bug is not resolved yet.
So only solution (without changing server behaviour) is to add your self-signed certificate to system's Trusted Root.
There is additional info about Secure client sockets in AIR and SecureSocket class.
Related
When I am try to connect the ROS using Realm Studio its says "The servers certificate could not be trusted"
Below is the screen-print :
I faced similar issue as you. But after reading Realm Studio does not trust SSL certificate of Realm Cloud on Linux #898 issue
Clicking "Reconnect, trusting the certificate" reloads the window but the same error is shown, endlessly. This was fixed with #905 but the issue of not automatically trusting the Realm Cloud certificate persists.
Users can now (once again) choose to trust the a certificate, but the issue remains that Studio does not automatically trust the Realm Cloud certificates of Realm Cloud.
I upgraded the realm studio to version 2.7.0 and attempted to reconnect. It worked.
Does anyone know the way to access IT Hit WebDAV Server's files from server side console application?
The DavContext generated inherits DavContextBaseAsync that depends on OwinContext or HttpContext.
Yes, you can mount file system using 'net use' command:
net use https://server/path/
Behind the scenes this command is using mini-redirector driver. After mounting you can use regular file system API and commands to manage the files on a WebDAV server.
Note that:
Your server must use Basic, Digest, NTLM, Kerberos authentication or
be anonymous. It does not support cookies/Forms authentication.
If you are using Basic authentication you need to use SSL/HTTPS or
enable insecure Basic authentication (for testing and dev purposes
only!)
If you are using 'net use' on the Windows Server you need to have
Desktop Experience Windows feature installed. By default this feature
is not installed on Windows Server.
I have a ASP.net web Project.
Many month ago my coworker tested my project in IIS with SSL self-certificate According to below link :
https://www.sslshopper.com/article-how-to-create-a-self-signed-certificate-in-iis-7.html
unfortunately my coworker doesn't be hear anymore and I don't know a lot about SSL Configuration in Project ! but I am expert in ASP.net and C# project
Right now our customers say "we need this project with TLS(V 1.2) Protocol Support" !
I know a little about TLS and I don't know how do I change my project for TLS certificate and what should I do for test it in IIS v 8.0 ? I heard TLS is next generation of SSl Protocol .
my OS is Win 8 .
Regards
I search in google and at last o found that I do this in 2 below step:
1- at first, I should handle SSL in IIS
https://www.sslshopper.com/article-how-to-create-a-self-signed-certificate-in-iis-7.html
2- at second, I must execute some script in power shell :
https://www.hass.de/content/setup-your-iis-ssl-perfect-forward-secrecy-and-tls-12
I have an old Flex application deployed in client machine. Now the certificate of the original application is expired. I purchased a new license from Godaddy and created a new AIR installer for my customers.
Now the problem is the new installer while running in Windows is giving the error below. The message below is not exact from the application but this is what it means:
The application cannot be installed due to a certificate problem. The
certificate does not match the installed application certificate, does
not support application upgrades, or is invalid. Please contact the
application author.
Now my question is, do I need to use the expired certificate and resign it and reuse it. Can't I use a new certificate. My ultimate goal is my customers should me able to install the application and that should override/update the old application.
My question is: why does a dev site work when the project is run in Visual Studio 2010, but not when served from IIS on the same PC?
I am trying to set up a dev copy of a client's site. On startup, the site makes a connection to a remote database server. The connection uses WCF and a SSL certificate to secure it. When I installed the site on my PC, following instructions, I installed a Cert Chain into the "Trusted Root Certification Authorities" and added registry keys and host entries to resolve connections to the remote service.
When I open the solution in Visual Studio 2010 on my PC and run it in the built-in ASP.NET dev server, it works -- my workstation connects to the remote service via SSL on a custom port (444) and the dev site queries for data successfully from the service. All of this is handled by a DLL provided with the project, and is outside my scope of work. I was briefed up front that the connection was very finicky about the SSL cert, system clock time agreement between the two machines, etc. and it took me a few tries to get it to work.
However, when I run the site in my local IIS (Windows 7, IIS 7.5) the site cannot connect to the remote service; the service won't accept the SSL connection. The startup code throws an exception when this happens, preventing the site from loading further.
Everything else seems to work fine: the only wrinkle is that VS requires a 32-bit version of the secure connection DLL while IIS on Windows 7 requires a 64-bit version. Both were provided to me and I swap them as required.
Per the comment, the answer is: check that the Cert Chain (to trust the SSL certificate used by the WCF connection) is installed to Local Machine (so that IIS sees it), not just to Current User (account used by Visual Studio).