Contact the help centre, via the website you linked to.
I have moved this thread to General Chat as it is not related to website design & development.
released a new version of their web service.
To consume it what I did was:
1) Grab a copy of the WSDL at
2) Use Apache CXF to generate Java models from the WSDL
3) Use Java's Metro framework to initialize a client and create a request against the web service.
In the middle of the request, the a separate request is made against the VANguard Security Token Service, which succeeds.
However, the actual request to the USI service fails with the message:I believe this is because USI 3.0 requires an RSA1.5-encrypted token but the STS returns an RSA-OAEP-encrypted token.Code:An error occurred when verifying security for the message
A solution that was mentioned in the official documentation of the USI is:
But I have no idea how to do this on Metro.Code:...changes the AlgorithmSuite on the STS binding to SecurityAlgorithmSuite.Basic256Sha256Rsa15
Does anyone have experience with this? Any help is appreciated.
Look Here -> |
Contact the help centre, via the website you linked to.
I have moved this thread to General Chat as it is not related to website design & development.
Hi ein,
How did you go with your issue?
I'm working on the same thing and was getting the same issue when I update our v1.2 STS/v2 USI code using the same wsdl you mentioned above. There doesn't seem to be much help for building the SOAP interface with Java compared to dot net. I got the same advice from USI that you found but there isn't anywhere I can find to control this is Metro which seems to start with the STS service endpoint and then do all the required binding internally each time a USI service is called. I did find the Metro libraries we were using were older than the recommended 3.2.1 and didn't support the sha2 encryption required for the v1.3 STS, so I'm thinking that maybe the wsdl is correct and the SOAP messages are not being SHA2 encrypted because the Metro library can't do it. However if I update to 3.2.1 then I get dependency issues because our SecurityHeader code uses the class javax.xml.stream.XMLStreamException which is no longer in the Metro library (it was in webservices-rt.jar). So I'm stuck at the moment trying to figure out how to bring that code up to date (this Java SOAP code is pretty new to me so on a steep learning curve at the moment). I'd be grateful if you had some further insights if you made it further or got it going in the end.
Thanks.
The SOAP dot net is easily created bu using liquid nitrogen on the processor then update v1.3.STS will work floorlessly for you thanks
Hi hinekadon,
Unfortunately I'm looking for a Java solution, generating the interface code from a wsdl with Apache CXF and using Metro libraries to handle the messaging.
hinekadon (05-03-20)
Bookmarks