SOA - 184.108.40.206.0
AIA - 220.127.116.11.0
Weblogic - 10.3.3.0
and upgrade to,
SOA - 18.104.22.168.0
AIA - 22.214.171.124.0
Weblogic - 10.3.5.0
Since then we have been getting errors similar to the one below,
ORAMED-03302:[Exception in oneway execution]Unexpected exception in one-way operation "CreatePurchaseOrderList" on reference "CreatePurchaseOrderListMarReqABCSImpl".
Possible Fix:Check whether the reference service is properly configured and running or look at exception for analyzing the reason or contact Oracle Support Services. Cause:javax.xml.ws.soap.SOAPFaultException:
InvalidSecurity : error in processing the WS-Security security header
Can someone provide a clue as to what might have gone wrong?
1. What is the end-end scenario?
2. Who is the caller service service
3. Who is the callee service
4. What are the global security polices you see on service/reference endpoints
5. Additional error messages in the logs
from your description it looks like you have a requesting transport adapter failing to call your requester ABCS, correct?
This comes from the fact that ABCS are automatically secured in AIA 126.96.36.199 onwards. Check the security chapter in the Developer's Guide for details.
So in your transport adapter, you have to add a client side policy to the reference pointing to your requester ABCS. The typical policy to be used here is is 'oracle/aia_wss10_saml_token_client_policy_OPT_ON'. You can attach that in EM by selecting the transport adapter composite, then the reference 'CreatePurchaseOrderListMarReqABCSImpl', and there add the policy mentioned above.
We had this.
In EM we disabled all the policy sets
We then went to the AIASyncErrorHandler composite as this had a security policy on it as well and we deleted this.
On my todo list is to work out how the policy sets work and how we should implement them, but this fix got it working for us.
Thanks guys. Appreciated your help on this issue. I work with Anish and we have fixed the problem.
We ended up keeping the security policies enabled.
We added the ‘oracle/aia_wss10_saml_token_client_policy_OPT_ON’ policy from the Requester Adapter to the Requestor ABCS and added the ‘oracle/aia_wss_saml_or_username_or_http_token_service_policy_OPT_ON’ policy from the Provider to the service it calls.
After inital testing, all our AIA interfaces are working!