Apple have decided to push all new or updated iOS applications into using HTTPS, starting in January 2017.

To subscribe by email, display this forum, scroll to the end and select ‘Subscribe Forum’.
Post Reply
MarkDuignan
Posts: 345
Joined: Tue Apr 17, 2012 7:33 pm

Apple have decided to push all new or updated iOS applications into using HTTPS, starting in January 2017.

Post by MarkDuignan » Mon Dec 05, 2016 9:17 pm

You might have noticed that the Internet world has been moving to HTTPS for a while now, for example Google searching.

Apple have decided to push all new or updated iOS applications into using HTTPS, starting in January 2017.

So when we next update LongRange, aXes Mobile or LANSA Mobile in the Apple App Store in 2017 you will need to be supporting HTTPS on your server to use them.

Many of your users automatically update their Apps, and there is no option to install earlier versions in the App Store, so you do need to be ready to use HTTPS.

If you do not use HTTPS
If you have a customized version of LongRange, aXes Mobile or LANSA Mobile then you are okay to keep using it until the next time it needs to be updated in the App Store.
Otherwise you need to start using HTTPS:
• You can switch over to HTTPS right now with your current version of any of all these products.
• You should be able to enable HTTPS alongside HTTP, which allows for non-disruptive initial testing and a graduated switchover.
• You need to switch everything over, including resources used in imbedded web views.
• If you use LongRange for RPG or aXes Mobile, you need to be using aXes 3.11 or later.
• If you use LongRange for LANSA or LANSA Mobile, you need to check that your IIS or Apache web server is using TLS 1.2 (or later).
See https://en.wikipedia.org/wiki/Transport ... ty#TLS_1.2

If you use HTTPS
You need to check:
• That you use HTTPS everywhere, including resources in imbedded web views.
• That you have, or can, make your certificate ‘trusted’ by installing your CA on every client device as the existing option Allow Invalid SSL Certificate can no longer be used.
See http://longrange.lansa.com.au/viewtopic.php?f=13&t=514
• If you use LongRange for RPG or aXes Mobile, you need to be using aXes 3.11, or later.
• If you use LongRange for LANSA or LANSA Mobile, you need to check that your IIS or Apache web server is using TLS 1.2 (or later). See https://en.wikipedia.org/wiki/Transport ... ty#TLS_1.2

Post Reply