Open GoogleCodeExporter opened 8 years ago
I tested on 4.0.3 phone and tablet and it works fine.
Really not sure, but maybe you must just reboot phone.
http://code.google.com/p/android/issues/detail?id=11231#c112
Original comment by supp.san...@gmail.com
on 12 May 2012 at 8:43
Original comment by supp.san...@gmail.com
on 15 May 2012 at 2:57
I have encountered the same problem. I cannot access https web page via client
certificate by samsung Galzxy SII default browser after upgraded to Android
4.03. Please kindly launch Sandrob for Android 4.03 version to solve the stuff.
Original comment by leo...@gmail.com
on 14 Aug 2012 at 5:07
There is no need for SandroB on 4.x android. From 4.0.3 certificates works fine
in native browser and even NTLM authentication is enabled.
There is sandroproxy that supports client certificates if your version of OS is
bellow 4.0.3
Original comment by supp.san...@gmail.com
on 14 Aug 2012 at 6:23
Unfortunately, Samsung removed the native browser and instead with his own
browser which not support the SSL Client Auth.
Original comment by anddyliu...@gmail.com
on 3 Oct 2012 at 8:55
Sorry to hear that.
Maybe this will work for you.
https://addons.mozilla.org/en-US/mobile/addon/cert-manager/
Original comment by supp.san...@gmail.com
on 3 Oct 2012 at 2:48
Do you have any information about the source of such fact?
<<Unfortunately, Samsung removed the native browser and instead with his own
browser which not support the SSL Client Auth.>>
I was wondering, why this doesn't work anymore ....
Original comment by martin.e...@zumtobel.com
on 4 Oct 2012 at 8:47
It would be somehow strange that they remove such a feature (client certs) from
their browser.
Probably is just port of native one.
Maybe I can enhance SandroProxy to be more secure and also use client certs
from android native certificate store...
Original comment by supp.san...@gmail.com
on 4 Oct 2012 at 2:27
just publish version of sslexample that should work on ics+:
https://play.google.com/store/apps/details?id=org.sandrob.sslexample
Original comment by supp.san...@gmail.com
on 28 Oct 2012 at 6:32
Original issue reported on code.google.com by
leitnerr...@gmail.com
on 12 May 2012 at 7:34