It doesn’t install the certificate as a trusted certificate on iOS. Accepting the certificate in Safari just adds an SSL exception that prevents Safari warning you about the site.This would allow you to open the site in Safari, but there are two significant downsides: It’s tempting to just select Continue or Details->Accept when you first try using your self-signed certificate in Safari: Tip #1 – Don’t Accept your Self-Signed Certificate in Mobile Safari The rest of this post provides tips on how to setup iOS to avoid these errors and how to simplify the creation and management of self signed certificates. The HttpWatch iOS app provides some more detail: In Mobile Safari you would see an error like this: The downside of using self-signed certificates is that browsers will not automatically trust sites that use them. Self-signed SSL certificates allow you to quickly create certificates for free, without having to pay a Certificate Authority (CA) or comply with any auditing requirements. You might need to setup SSL on development and test servers that have different host names or on systems that will only ever be accessed on your local network. SSL certificates are relatively cheap to purchase, but sometimes it would be easier if you could create your own. Five Tips for Using Self Signed SSL Certificates with iOS
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |