|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
I have a a hacky way to do this in this commit: https://github.com/pilhuhn/RHQpocket/commit/ea3a1e571eb9930b7875f9ec92a6f3ae2d5aef5a#diff-ca56432755acbdbb38d01b64b5eaf60aR86
What I think AG should do is to catch the `javax.net.ssl.SSLHandshakeException` and then pop up a requestor "the cert is unknown do you want to trust it - yes, no , always, maybe" and similar for the hostname verification. AG should then store that in e.g. shared preferences of the app.