You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-dev@ws.apache.org by bu...@apache.org on 2003/03/09 16:15:44 UTC
Bug report for Apache SOAP [2003/03/09]
+---------------------------------------------------------------------------+
| Bugzilla Bug ID |
| +---------------------------------------------------------------------+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned |
| | OPN=Reopened VER=Verified (Skipped Closed/Resolved) |
| | +-----------------------------------------------------------------+
| | | Severity: BLK=Blocker CRI=Critical MAJ=Major |
| | | MIN=Minor NOR=Normal ENH=Enhancement |
| | | +-------------------------------------------------------------+
| | | | Date Posted |
| | | | +--------------------------------------------------+
| | | | | Description |
| | | | | |
| 2209|New|Nor|2001-06-18|Send XML data as a string? |
|10716|Ass|Maj|2002-07-11|Can't unmarshall xsi:nil="true" if xsi:type is mis|
|11370|Ass|Maj|2002-08-01|Error: 500 :Location: /apache-soap/admin/list.jsp |
|11672|New|Nor|2002-08-13|RPCRouter specification of ConfigFile restrictive |
|12495|Ass|Maj|2002-09-10|NullPointerException in RPCRouter when invoking St|
|12743|Ass|Cri|2002-09-17|Method execution fails at huge SOAP-Parameters |
|12834|Ass|Cri|2002-09-19|Fails on certain parameter names. |
|14001|New|Maj|2002-10-27|Content-Length field parsing not according to RFC |
|14865|New|Blk|2002-11-26|start and Content-ID differ |
|15666|New|Nor|2002-12-26|"Deployed Service Information page" is uncomfortab|
|16007|New|Nor|2003-01-12|All attempts to configure Apache SOAP fail |
|16356|New|Maj|2003-01-23|faultcode is not recognized as an element in the F|
|17334|New|Nor|2003-02-24|Problem to config Soap 2.3 + Tomcat 4.0.5 + xerces|
|17335|New|Nor|2003-02-24|Problem to config Soap 2.3 + Tomcat 4.0.5 + xerces|
|17643|New|Min|2003-03-04|patch for org.apache.soap.encoding.Hex |
|17755|New|Nor|2003-03-07|Version information in MANIFEST.MF file. |
+-----+---+---+----------+--------------------------------------------------+
| Total 16 bugs |
+---------------------------------------------------------------------------+
Https with call.invoke()
Posted by Trimarchi Michele <Mi...@crypto.it>.
Hi there..
i have a servlet,on a web application , that calls a webservice via https
(on a separate .net environment) ,
i'm using rpc style with classic call.invoke()..
Everything works great and without any problem but i've a big doubt.
I'm using system.setProperty methods to set
keystore,truststore,keystorepassword,truststore and so on.
I think this solution is not very smart .When i will have to deploy another
web application with https soap calls what will i have to do?? I don't think
it will be very prudent to setProperty() again with different keystore path
and password and overwrite jvm properties set by the first webapp.
so,the question is:
is it possible to setting keystore and truststore just for the servlet scope
without using system properties?
I can make it for an https url connection
SSLSocketFactory ssf;
TrustManagerFactory tmf;
KeyStore ks;
FileInputStream fis;
String pathKeyStore="C:\\client.keystore";
char[] passphrase = "keystorePassword".toCharArray();
fis=new FileInputStream(pathKeyStore);
ks = KeyStore.getInstance("JKS");
ks.load(fis, passphrase);
tmf = TrustManagerFactory.getInstance("SunX509");
tmf.init(ks);
SSLContext ctx = SSLContext.getInstance("TLS");
ctx.init(null, tmf.getTrustManagers(), null);
fis.close();
try {
URL url = new URL("https://yourpage");
com.sun.net.ssl.HttpsURLConnection connection =
(com.sun.net.ssl.HttpsURLConnection) url.openConnection();
ssf = ctx.getSocketFactory();
connection.setSSLSocketFactory(ssf);
connection.connect();
System.out.println("Ok :" + connection.getURL());
..but i don't know how make call.invoke() work ..the servlet throws
"untrusted server chain" exception..
Any hints?
Thanks in advance
Michele