我正在开发通过HTTP客户端,需要访问快速支付的服务的Android应用程序(https://secure.quickpay.dk/form)。不过,我一直访问该页面时收到错误信息。更具体地讲,我得到一个没有对等证书的错误消息。我尝试了几种不同的东西早已: 我尝试添加根证书到我的密钥库,并在连接时使用这个密钥库,以下步骤:的添加证书密钥库。 我也试着接受所有的证书,从这里所提出的方法如下:accepting证书机器人。 我已经成功连接到其他https网站,但似乎无法连接到这一个。我曾尝试在不同的Android设备(1.6,2.2和2.3.3)。在连接到快速支付的网站任何人都可以成功,或者任何人都可以想出一个可行的解决方案/修复?
//更新:如果我进入这个网站和我的WebView:支付窗口的例子和preSS一个按钮(这基本上只是启动一个HTTP POST一些pre定义的变量),我能够连接到该网站中的WebView Android上2.3.3。此外,我发现我得到的答复从网站,如果我尝试启动上述程序在Android 3.1!有什么建议?
公共类MyHttpClient扩展DefaultHttpClient {
最后上下文的背景下;
公共MyHttpClient(上下文的背景下){
this.context =背景;
loadHttps();
}
私人无效loadHttps(){
字符串URL =https://secure.quickpay.dk/form;
HttpPost httpPost =新HttpPost(URL);
尝试 {
的System.out.println(执行);
this.execute(httpPost);
}赶上(UnsupportedEncodingException E){
的System.out.println(e.getMessage());
}赶上(ClientProtocolException E){
的System.out.println(e.getMessage());
}赶上(IOException异常E){
的System.out.println(E);
}
}
@覆盖
保护ClientConnectionManager createClientConnectionManager(){
SchemeRegistry注册表=新SchemeRegistry();
registry.register(新计划(HTTP,PlainSocketFactory.getSocketFactory(),80));
registry.register(新计划(https开头,newSslSocketFactory(),443));
返回新SingleClientConnManager(getParams()方法,登记);
}
私人的SSLSocketFactory newSslSocketFactory(){
尝试 {
密钥仓库中可信任= KeyStore.getInstance(BKS);
InputStream的时间= context.getResources()openRawResource(R.raw.test)。
尝试 {
trusted.load(在mysecret.toCharArray());
} 最后 {
附寄();
}
SSLSocketFactory的SF =新的SSLSocketFactory(信任);
返回SF;
}赶上(例外五){
抛出新的AssertionError(E);
}
}
}
堆栈跟踪:
WARN / System.err的(8459)在org.apache.harmony.xnet.provider.jsse.SSLSessionImpl.getPeerCertificates(SSLSessionImpl.java 258)
WARN / System.err的(8459)在org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java 93)
在org.apache.http.conn.ssl.SSLSocketFactory.createSocket(SSLSocketFactory.java 381)WARN / System.err的(8459)
在WARN / System.err的(8459) org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java 177)
在org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java 164)WARN / System.err的(8459)
在org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java 119)WARN / System.err的(8459)
在org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java 359)WARN / System.err的(8459)
在org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java 555)WARN / System.err的(8459)
在org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java 487)WARN / System.err的(8459)
在org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java 465)WARN / System.err的(8459)
在test.https.MyHttpClient.loadHttps(MyHttpClient.java 34)WARN / System.err的(8459)
WARN / System.err的(8459)在test.https.MyHttpClient< INIT>(MyHttpClient.java 26)
WARN / System.err的(8459)在test.https.HttpsTesterActivity.onCreate(HttpsTesterActivity.java 60)
在android.app.Instrumentation.callActivityOnCreate(Instrumentation.java 1047)WARN / System.err的(8459)
在android.app.ActivityThread.performLaunchActivity WARN / System.err的(8459)(ActivityThread.java 1615)
在android.app.ActivityThread.handleLaunchActivity WARN / System.err的(8459)(ActivityThread.java 1667)
WARN / System.err的(8459)在android.app.ActivityThread.access $ 1500(ActivityThread.java 117)
WARN / System.err的(8459)在android.app.ActivityThread $ H.handleMessage(ActivityThread.java 935)
在android.os.Handler.dispatchMessage(Handler.java 99)WARN / System.err的(8459)
在android.os.Looper.loop(Looper.java 123)WARN / System.err的(8459)
在android.app.ActivityThread.main WARN / System.err的(8459)(ActivityThread.java 3687)
在java.lang.reflect.Method.invokeNative WARN / System.err的(8459)(本机方法)
在java.lang.reflect.Method.invoke(Method.java 507)WARN / System.err的(8459)
WARN / System.err的(8459)在com.android.internal.os.ZygoteInit $ MethodAndArgsCaller.run(ZygoteInit.java 842)
在com.android.internal.os.ZygoteInit.main(ZygoteInit.java 600)WARN / System.err的(8459)
解决方案
只是总结一下,我所坚持的web视图的方法解决了这个问题。与API的相互作用被转移到一个服务器,创建用于处理证书问题的中间通信点。没有最完美的解决方案,但它的工作原理:)
I am developing an Android application which needs to access QuickPay's service ("https://secure.quickpay.dk/form") through an Http-client. But I keep getting errors when accessing the page. More specifically I get a "No Peer Certificate" error message. I tried several different things already: I tried adding the root certificate to my keystore, and to use this keystore when connecting, following this procedure: adding certificate to keystore. I also tried accepting all certificates, following the proposed method from here: accepting certificate for android. I have successfully connected to other https sites, but can not seem to connect to this one. I have tried on different Android devices (1.6, 2.2, and 2.3.3). Can anyone succeed in connecting to quickpay's site, or can anyone come up with a possible solution/fix?
//Update: If I access this site with my WebView: payment window examples, and press one of the buttons (which basically just launches a http post with some pre-defined variables) I am able to connect to the site in the webview on Android 2.3.3. Furthermore, I found out that I get a reply from the site if I try to launch the above application on Android 3.1! Any suggestions?
public class MyHttpClient extends DefaultHttpClient {
final Context context;
public MyHttpClient(Context context) {
this.context = context;
loadHttps();
}
private void loadHttps() {
String url = "https://secure.quickpay.dk/form";
HttpPost httpPost = new HttpPost(url);
try {
System.out.println("Executing");
this.execute(httpPost);
} catch (UnsupportedEncodingException e) {
System.out.println(e.getMessage());
} catch (ClientProtocolException e) {
System.out.println(e.getMessage());
} catch (IOException e) {
System.out.println(e);
}
}
@Override
protected ClientConnectionManager createClientConnectionManager() {
SchemeRegistry registry = new SchemeRegistry();
registry.register(new Scheme("http", PlainSocketFactory.getSocketFactory(), 80));
registry.register(new Scheme("https", newSslSocketFactory(), 443));
return new SingleClientConnManager(getParams(), registry);
}
private SSLSocketFactory newSslSocketFactory() {
try {
KeyStore trusted = KeyStore.getInstance("BKS");
InputStream in = context.getResources().openRawResource(R.raw.test);
try {
trusted.load(in, "mysecret".toCharArray());
} finally {
in.close();
}
SSLSocketFactory sf = new SSLSocketFactory(trusted);
return sf;
} catch (Exception e) {
throw new AssertionError(e);
}
}
}
StackTrace:
WARN/System.err(8459) at org.apache.harmony.xnet.provider.jsse.SSLSessionImpl.getPeerCertificates(SSLSessionImpl.java 258)
WARN/System.err(8459) at org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java 93)
WARN/System.err(8459) at org.apache.http.conn.ssl.SSLSocketFactory.createSocket(SSLSocketFactory.java 381)
WARN/System.err(8459) at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java 177)
WARN/System.err(8459) at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java 164)
WARN/System.err(8459) at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java 119)
WARN/System.err(8459) at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java 359)
WARN/System.err(8459) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java 555)
WARN/System.err(8459) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java 487)
WARN/System.err(8459) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java 465)
WARN/System.err(8459) at test.https.MyHttpClient.loadHttps(MyHttpClient.java 34)
WARN/System.err(8459) at test.https.MyHttpClient.<init>(MyHttpClient.java 26)
WARN/System.err(8459) at test.https.HttpsTesterActivity.onCreate(HttpsTesterActivity.java 60)
WARN/System.err(8459) at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java 1047)
WARN/System.err(8459) at android.app.ActivityThread.performLaunchActivity(ActivityThread.java 1615)
WARN/System.err(8459) at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java 1667)
WARN/System.err(8459) at android.app.ActivityThread.access$1500(ActivityThread.java 117)
WARN/System.err(8459) at android.app.ActivityThread$H.handleMessage(ActivityThread.java 935)
WARN/System.err(8459) at android.os.Handler.dispatchMessage(Handler.java 99)
WARN/System.err(8459) at android.os.Looper.loop(Looper.java 123)
WARN/System.err(8459) at android.app.ActivityThread.main(ActivityThread.java 3687)
WARN/System.err(8459) at java.lang.reflect.Method.invokeNative(Native Method)
WARN/System.err(8459) at java.lang.reflect.Method.invoke(Method.java 507)
WARN/System.err(8459) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java 842)
WARN/System.err(8459) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java 600)
解决方案
Just to sum up, I fixed this issue by sticking to the WebView approach. The interaction with the API was moved to a server, creating an intermediate communication point which handles the certificate issues. Not the most elegant solution but it works :)