Contributions
Re: X509 certificate
I think you might use the WSS4J in an incorrect way. Read the last 3 comments, they are about SoapUI. https://issues.apache.org/jira/browse/WSS-200 I just want to try to use the "SKI_KEY_IDENTIFIER" instead of the X509_KEY_IDENTIFIER to very if this is the problem.3.2KViews0likes0CommentsRe: X509 certificate
More info: This is signature is generated with SoapUI 3.0 (Signature Algorithm = X509 Certificate) - - MIIEFzC...... If I read the standard, http://docs.oasis-open.org/wss/2004/01/ ... le-1.0.pdf, (page=8, line 209). Then it says that the ValueTypeUri has to be "X509 SubjectKeyIdentifier". This is not the case in SoapUI as you can see above. Is this an error in SoapUI or am I reading the standard in a wrong way. If I change Sequrity Algorithm to Binary Sequrity Token it work fine.3.2KViews0likes0CommentsRe: The signature or decryption was invalid
Hi, I might have the same problem. This is signature is generated with SoapUI 3.0 (Signature Algorithm = X509 Certificate) - - MIIEFzC...... If I read the standard, http://docs.oasis-open.org/wss/2004/01/ ... le-1.0.pdf, (page=8, line 209). Then it says that the ValueTypeUri has to be "X509 SubjectKeyIdentifier". This is not the case in SoapUI as you can see above. Is this an error in SoapUI or am I reading the standard in a wrong way. If I change Sequrity Algorithm to Binary Sequrity Token it work fine.12KViews0likes0CommentsRe: XML signature
Hi, I have attached my project to this mail. I would like to know more about the signature part. Have I generated it correct? The server that I sent the message to give me an error for the SignatureValue. If I compare it to other request the generated soapUI request is missing a prefix list. /Fredrik850Views0likes0CommentsXML signature
I am trying to create a request with XML signature with soapUI. The created message looks like this: 1xeWb10a3EIXvGOSPh/82tjxul4= Bv20lY0H4QM6JCOan......xtPm6N7kEiGnfwVFeSMSfXqyQ== MIIEDj.....Ap+oBbPcw== urn:carelink:bif:authz:0.1:EvaluateXACML30Request anyType The problem I have is that the server reject my message: "Verification of Signature with ID Signature-10748469 failed, possible cause : proper canonicalizedsignedinfo was not produced." It looks likte it is impossible to calculate the value for the server. What I am missing in the request is a prefix list. Example: ==> ==> RSYxyDk+tlgcNt/C+SUq6rU7tJQ= So, my question is if you use prefix in your calculation but the prefix list is not added in the request?2KViews0likes2CommentsRe: WSDL security
Hi again, Don't know if I missunderstand you. Today I have configured my security header in the "Security Configurations" (TimeStamp, Signature). To activate this security header I open the request and select "Aut" tab and press the "outgoing WSS" button where I can select my security configuration. I also select the "WS-A" tab and select the checkbutton (Enable WS-A addressing). If I understan you correct I should remove all above and intead create my own security header. That is no problem, I have examples of headers so I can just copy and paste them. But I do not know where I can add not find where I can add this security header in soapUI. PS! We have bought IBM Rational Soa Tester for $$$$ and it can not handle SAML2.0 either. So I have requested a soapUIpro license now. A looked at your video and I think we can do the same performance tests with this tool so maybe we can kick out IBM now. :-)947Views0likes0Comments