We should add an option to configure TLS validation strategy applied to the library's internal networking code. This is typically welcomed by an application developers who has multiple non-production server environments configured with self-signed, or invalid certificates.
There will be two basic validation strategies provided by the library:
System TLS handling configured as default. So if developer doesn't touch this option, then library will work as before.
Strategy that will allow untrusted TLS certificates, for development purposes.
We should add an option to configure TLS validation strategy applied to the library's internal networking code. This is typically welcomed by an application developers who has multiple non-production server environments configured with self-signed, or invalid certificates.
There will be two basic validation strategies provided by the library:
Similar feature is already implemented in our PowerAuth Mobile SDK.