RE: [wsf-php-user] key failure *update*

2007-10-15 Thread shams jawaid 

HI, just wanted to say that, 
 
in using tomcat 5.5 i used axis2 1.2, and tomcat 6 - axis2 1.3 for my example.
 
thanks


From: [EMAIL PROTECTED]: [EMAIL PROTECTED]; [EMAIL PROTECTED]: [EMAIL 
PROTECTED]: RE: [wsf-php-user] key failureDate: Mon, 15 Oct 2007 05:51:38 +


Hi kaushalye,  i did this in tomcat 5.5 then in tomcat 6. i attached both the 
outputs in the tomcat window and in tcpmon,  thanks  Date: Mon, 15 Oct 2007 
11:07:12 +0530 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] CC: [EMAIL 
PROTECTED]; axis-user@ws.apache.org Subject: Re: [wsf-php-user] key failure  
Hi Shams, I think if you could attach a trace of the SOAP message, 
Rampart/Java  guys may be able to find the reason for the fault string in the 
 response. The complaint is about a missing encryption result for an  
Id(NULL?), which they have to match with the message. The PHP client and  its 
configurations seems to be correct. -Kaushalye  shams jawaid wrote:  Hi, 
   i am currently trying to encrypt and sign a simple service from a php   
client to a java web service. the request is encrypted and signed, but   the 
service side response recieves this error in tcpmon:
faultstringMissing encryption result for id : /faultstringand in 
tomcat, this is the output:INFO: Server startup in 3734 ms  [INFO] 
Verification successful for URI '#SigID-402a0180-2c19-4f2e'  [INFO] 
Verification successful for URI '#SigID-a673ae2e-5835-4d1f'in my client 
side, i have included the keys:$my_cert = 
ws_get_cert_from_file('alice_cert.cert'); // client side   certificate( 
public key)  $my_key = ws_get_key_from_file('alice_key.pem'); // client side 
key  $rec_cert = ws_get_cert_from_file('bob_cert.cert'); // server side   
certificate (public key )and in my service side key (service.jks) 
referenced like this:ramp:signatureCrypto  ramp:crypto 
provider='org.apache.ws.security.components.crypto.Merlin'  ramp:property  
 
name='org.apache.ws.security.crypto.merlin.keystore.type'JKS/ramp:property 
 ramp:property   
name='org.apache.ws.security.crypto.merlin.file'service.jks/ramp:property  
ramp:property   
name='org.apache.ws.security.crypto.merlin.keystore.password'apache/ramp:property
  /ramp:crypto  /ramp:signatureCrypto  ramp:encryptionCypto  
ramp:crypto provider='org.apache.ws.security.components.crypto.Merlin'  
ramp:property   
name='org.apache.ws.security.crypto.merlin.keystore.type'JKS/ramp:property 
 ramp:property   
name='org.apache.ws.security.crypto.merlin.file'service.jks/ramp:property  
ramp:property   
name='org.apache.ws.security.crypto.merlin.keystore.password'apache/ramp:property
  /ramp:crypto  /ramp:encryptionCypto  /ramp:RampartConfigi 
have includeded :[1] alice_cert  [2] bob_cert  [3] bob_key 
(although i am unsure whether this was imported properly,   and am thinking 
this might be the cause of the error)i have attached my 
service.properties, service.jks, PWCBHandler.class,   services.xml and my 
service file.i have also attached my client side files including the 
alice_key,   alice_cert, bob_cert, php client file and the policy.xml file. 
   If anyone can solve this error out there it would be a tremendous   
help, or if anyone can create a keystore properly if i have not done   so, 
please do. i suspect this is the reason why. the keystore attached   is 
service.jksthanks alot!   
  The 
next generation of MSN Hotmail has arrived - Windows Live Hotmail   
http://www.newhotmail.co.uk  
   
___  Wsf-php-user mailing list  
[EMAIL PROTECTED]  http://wso2.org/cgi-bin/mailman/listinfo/wsf-php-user   
  --  http://kaushalye.blogspot.com/ http://wso2.org/ 

The next generation of MSN Hotmail has arrived - Windows Live Hotmail 
_
100’s of Music vouchers to be won with MSN Music
https://www.musicmashup.co.uk

RE: [wsf-php-user] key failure

2007-10-14 Thread shams jawaid 

Hi kaushalye,  i did this in tomcat 5.5 then in tomcat 6. i attached both the 
outputs in the tomcat window and in tcpmon,  thanks  Date: Mon, 15 Oct 2007 
11:07:12 +0530 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] CC: [EMAIL 
PROTECTED]; axis-user@ws.apache.org Subject: Re: [wsf-php-user] key failure  
Hi Shams, I think if you could attach a trace of the SOAP message, 
Rampart/Java  guys may be able to find the reason for the fault string in the 
 response. The complaint is about a missing encryption result for an  
Id(NULL?), which they have to match with the message. The PHP client and  its 
configurations seems to be correct. -Kaushalye  shams jawaid wrote:  Hi, 
   i am currently trying to encrypt and sign a simple service from a php   
client to a java web service. the request is encrypted and signed, but   the 
service side response recieves this error in tcpmon:
faultstringMissing encryption result for id : /faultstringand in 
tomcat, this is the output:INFO: Server startup in 3734 ms  [INFO] 
Verification successful for URI '#SigID-402a0180-2c19-4f2e'  [INFO] 
Verification successful for URI '#SigID-a673ae2e-5835-4d1f'in my client 
side, i have included the keys:$my_cert = 
ws_get_cert_from_file('alice_cert.cert'); // client side   certificate( 
public key)  $my_key = ws_get_key_from_file('alice_key.pem'); // client side 
key  $rec_cert = ws_get_cert_from_file('bob_cert.cert'); // server side   
certificate (public key )and in my service side key (service.jks) 
referenced like this:ramp:signatureCrypto  ramp:crypto 
provider='org.apache.ws.security.components.crypto.Merlin'  ramp:property  
 
name='org.apache.ws.security.crypto.merlin.keystore.type'JKS/ramp:property 
 ramp:property   
name='org.apache.ws.security.crypto.merlin.file'service.jks/ramp:property  
ramp:property   
name='org.apache.ws.security.crypto.merlin.keystore.password'apache/ramp:property
  /ramp:crypto  /ramp:signatureCrypto  ramp:encryptionCypto  
ramp:crypto provider='org.apache.ws.security.components.crypto.Merlin'  
ramp:property   
name='org.apache.ws.security.crypto.merlin.keystore.type'JKS/ramp:property 
 ramp:property   
name='org.apache.ws.security.crypto.merlin.file'service.jks/ramp:property  
ramp:property   
name='org.apache.ws.security.crypto.merlin.keystore.password'apache/ramp:property
  /ramp:crypto  /ramp:encryptionCypto  /ramp:RampartConfigi 
have includeded :[1] alice_cert  [2] bob_cert  [3] bob_key 
(although i am unsure whether this was imported properly,   and am thinking 
this might be the cause of the error)i have attached my 
service.properties, service.jks, PWCBHandler.class,   services.xml and my 
service file.i have also attached my client side files including the 
alice_key,   alice_cert, bob_cert, php client file and the policy.xml file. 
   If anyone can solve this error out there it would be a tremendous   
help, or if anyone can create a keystore properly if i have not done   so, 
please do. i suspect this is the reason why. the keystore attached   is 
service.jksthanks alot!   
  The 
next generation of MSN Hotmail has arrived - Windows Live Hotmail   
http://www.newhotmail.co.uk  
   
___  Wsf-php-user mailing list  
[EMAIL PROTECTED]  http://wso2.org/cgi-bin/mailman/listinfo/wsf-php-user   
  --  http://kaushalye.blogspot.com/ http://wso2.org/ 
_
100’s of Music vouchers to be won with MSN Music
https://www.musicmashup.co.ukPOST /axis2/services/Math HTTP/1.1
User-Agent: Axis2/C
SOAPAction: urn:add
Content-Length: 6765
Content-Type: text/xml;charset=UTF-8
Host: 127.0.0.1:8181

soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
   soapenv:Header xmlns:wsa=http://www.w3.org/2005/08/addressing;
  wsa:Tohttp://localhost:8181/axis2/services/Math/wsa:To
  wsa:Actionurn:add/wsa:Action
  wsa:MessageIDe7f67741-40fb-4c26-8a46-75bb6fc877c1/wsa:MessageID
  wsse:Security soapenv:mustUnderstand=1 
xmlns:wsse=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd;
 wsse:BinarySecurityToken 
EncodingType=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary;
 wsu:Id=CertID-928c531c-c47f-46a2 
ValueType=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3;
 
xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd;MIIDDDCCAfSgAwIBAgIQM6YEf7FVYx/tZyEXgVComTANBgkqhkiG9w0BAQUFADAwMQ4wDAYDVQQKDAVPQVNJUzEeMBwGA1UEAwwVT0FTSVMgSW50ZXJvcCBUZXN0IENBMB4XDTA1MDMxOTAwMDAwMFoXDTE4MDMxOTIzNTk1OVowQjEOMAwGA1UECgwFT0FTSVMxIDAeBgNVBAsMF09BU0lTIEludGVyb3AgVGVzdCBDZXJ0MQ4wDAYDVQQDDAVBbGljZTCBnzANBgkqhkiG9w0BAQEFAA