Hello,
I have a WebSocket server running locally on 127.0.0.1 inside my iOS app using SwiftNIO Transport Services.
This WebSocket server is using a certificate with 127.0.0.1 name signed by a custom root certificate which is self-signed (so not trusted by default).
Inside my app, I open a WKWebView and some JavaScript inside the webpage I navigate to is able to connect to my server with WebSocket secure protocol (wss) to send JSON formatted command to be executed natively in the app and send back a response.
The javascript client library is based on universal-websocket-client npm library which is based on the native WebSocket Web API of the browser. I control also this library.
In order for this to work, I have to install manually the profile of the root certificate and to trust it explicitly in the settings.
I would like to avoid having the user to manually make an action to trust this certificate because perhaps I'd like to put my app at the end in the App Store.
I don't need this certificate to be trusted for the whole device, just for my app.
Is there any option that I have to do so ?
For example by prompting the user inside the app to trust the root or even doing it silently for the user ? Perhaps by adding the custom root CA into the keychain ?
I tried to look at having a certificate signed by a known CA but for 127.0.0.1, I guess it's not possible.
I tried also to look at the trust evaluation but I'm the server, not the client. And on the javascript side, using the native WebSocket API, it seems that I cannot supplement with my custom CA when making the connection or override the trust evaluation. Or can I ?
Thank you in advance for any help.
Christophe
I have a WebSocket server running locally on 127.0.0.1 inside my iOS app using SwiftNIO Transport Services.
This WebSocket server is using a certificate with 127.0.0.1 name signed by a custom root certificate which is self-signed (so not trusted by default).
Inside my app, I open a WKWebView and some JavaScript inside the webpage I navigate to is able to connect to my server with WebSocket secure protocol (wss) to send JSON formatted command to be executed natively in the app and send back a response.
The javascript client library is based on universal-websocket-client npm library which is based on the native WebSocket Web API of the browser. I control also this library.
In order for this to work, I have to install manually the profile of the root certificate and to trust it explicitly in the settings.
I would like to avoid having the user to manually make an action to trust this certificate because perhaps I'd like to put my app at the end in the App Store.
I don't need this certificate to be trusted for the whole device, just for my app.
Is there any option that I have to do so ?
For example by prompting the user inside the app to trust the root or even doing it silently for the user ? Perhaps by adding the custom root CA into the keychain ?
I tried to look at having a certificate signed by a known CA but for 127.0.0.1, I guess it's not possible.
I tried also to look at the trust evaluation but I'm the server, not the client. And on the javascript side, using the native WebSocket API, it seems that I cannot supplement with my custom CA when making the connection or override the trust evaluation. Or can I ?
Thank you in advance for any help.
Christophe
