How to use a self-signed SSL certificate when developing with Trigger.io?

Question

Our backend is on rails, and for several reasons, the development environment should run on rails using a self-signed SSL certificate. This works fine on the desktop after manually authenticating the certificate.

Using Trigger.io, we are developing a mobile application focused on iOS from the same backend. It would be ideal for us to be able to start the rail server using SSL (so that we can compare the output of the browser) and still have the iOS simulator connect correctly without complaining about invalid certificates.

The production uses the correct ssl-cert, but what is the best way to configure the simulator?

Answer 1

You can try installing the CRT file on the device as follows:

• Push your CRT file to a server to which your device can access

• On the device, go to http://example.com/certificate.crt , then install the certificate.

This is similar to how you can debug SSL with a proxy server, as described here

Answer 2

For testing purposes, you can create a category around NSURLRequest that ignores certificates:

@implementation NSURLRequest (IgnoreSSL) + (BOOL)allowsAnyHTTPSCertificateForHost:(NSString*)host { return YES; } @end 

This clearly cannot be sent to the application store and should not be used during production.