Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Custom SSL truststore on Android #485

Closed
don-spyker opened this issue May 28, 2019 · 2 comments
Closed

Support Custom SSL truststore on Android #485

don-spyker opened this issue May 28, 2019 · 2 comments

Comments

@don-spyker
Copy link

Feature Request

Motivation Behind Feature

If the inappbrowser should connect to a website via https and the SSL certificate is self-signed or issued/created with a company's root certificate the inappbrowser is not opening the website. This is also the case if you install the custom certificate on the device. The access to the website works when using target '_self' or target '_system', but not when using target '_blank'.
The inappbrowser is not even handling the error, but that is handled in #292. This issue is about enabling the inappbrowser to use the a custom truststore.

On iOS the inappbrowser is already trusting all certificates that are enabled on the devices. This issue targets Android.

Feature Description

Trust a custom certificate to avoid SSL errors while opening a website that is secured with a non public root CA.

Alternatives or Workarounds

Use target '_self' or target '_system' -> not appropriate in all cases
Use public CA -> -> not appropriate in all cases

@chiluhimanshu2221
Copy link

chiluhimanshu2221 commented Apr 8, 2020

This is not the plugin issue. Android had following handshake rules to communicate with self signed ssl . I have resolved my issue by using certificate inside my build. Please follow https://developer.android.com/training/articles/security-config

@timbru31
Copy link
Member

timbru31 commented Apr 8, 2020

Thanks @chiluhimanshu2221

@timbru31 timbru31 closed this as completed Apr 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants