Hello. I'm developing application that helps user with Wi-Fi connectivity. This application works with special hotspots. It supports are generally 2 types of hotspots: WPA2 (EAP-TLS) and WISPr. I have couple of questions about capabilities of NEHotspotHelper.
1. WPA2 Connectivity: if I clearly understand the only way to avoid user interaction with connection process is to add this known hotspots SSIDs to .mobileconfig and install it. And there is no way to programmatically install .mobileconfig to device keychain, correct? So, only way to install .mobileconfig is to place it on remote server and open link to file in Safari browser (or mail app).
2. WISPr connectivity: My aim is to avoid any user interaction with connectivity process. I use NEHotspotHelper to get callbacks when necessary hotspot is connected and programmatically authenticate on Captive Portal. So, when my application is running, it works like a charm. But, if user "kill" application, my app lose control in some cases: if user connect to Captive network when my app not running, my hotspot helper doesn't recognize connection. Connection is just recognized by system hotspot helper.
So, my questions:
1. Is it possible to get callback when my app is killed? Maybe there are way to suggest user to run my app? Any "legal" way. Maybe it possible with mobileconfig?
2. Is it possible to set high confidence to my network on start app when my hotspot already connected?
3. Is it possible to get access to system keychain, modify it, or at least read (check is certificate is valid or expired).
I'm will be grateful for any information which you can give me.