-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
mTls Client Certificate authentication not working as in Android #2267
Comments
NOTE: This comment is auto-generated. Are you sure you have already searched for the same problem? Some people open new issues but they didn't search for something similar or for the same issue. Please, search for it using the GitHub issue search box or on the official inappwebview.dev website, or, also, using Google, StackOverflow, etc. before posting a new one. You may already find an answer to your problem! If this is really a new issue, then thank you for raising it. I will investigate it and get back to you as soon as possible. Please, make sure you have given me as much context as possible! Also, if you didn't already, post a code example that can replicate this issue. In the meantime, you can already search for some possible solutions online! Because this plugin uses native WebView, you can search online for the same issue adding Following these steps can save you, me, and other people a lot of time, thanks! |
We are getting the same error message here for Android... the code looks basically the same. With 5.8.0, the problem did not occur, but we cannot use that version anymore. I tried 6.1.5 and 6.2.0-beta.2. Also, with the certificate test site badssl.com, the same code is working fine.
And here is the console output:
I tried to add 'selectedCertificate: 0' to the ClientCertResponse despite it being flagged as Windows only, but as expected, with the exact same output. I hope this helps to further analyse the ticket. |
But the ios system is normal
inappwebview 6.0.0
Can I get any suggestions for solving the error?
Thanks!
The text was updated successfully, but these errors were encountered: