on 09-03-2015 12:26 PM
Hi All,
We have a scenario that requires us to do header level Authentication on a SOAP call. We are using the SOAP Axis adapter. But we get an error as soon as the third party adds the timestamp in the header. The message does works if we remove the timestamp, but the third party cannot remove it from the payload. I know that we can remove it using a custom adapter module, but that is a last resort. We would like to get the Axis adapter working.
Error - WSDoAllReceiver: The timestamp could not be validated
Please see my configuration below.
Process Sequence:
1 | AF_Adapters/axis/HandlerBean | Local Enterprise Bean | auth |
2 | AF_Adapters/axis/HandlerBean | Local Enterprise Bean | usertoken |
3 | AF_Adapters/axis/HandlerBean | Local Enterprise Bean | login |
4 | AF_Adapters/axis/HandlerBean | Local Enterprise Bean | xireq |
5 | AF_Adapters/axis/AFAdapterBean | Local Enterprise Bean | afreq |
6 | CallSapAdapter | Local Enterprise Bean | sap |
7 | AF_Adapters/axis/AFAdapterBean | Local Enterprise Bean | afresp |
8 | AF_Adapters/axis/HandlerBean | Local Enterprise Bean | xires |
Module Configuration:
1 | auth | handler.type | java:org.apache.axis.handlers.http.HTTPAuthHandler |
2 | login | handler.type | java:com.sap.aii.adapter.axis.ra.handlers.security.LoginHandler |
3 | sap | module.pivot | true |
4 | usertoken | action | UsernameToken Timestamp |
5 | usertoken | handler.type | java:com.sap.aii.adapter.axis.ra.handlers.security.WSDoAllReceiver |
6 | usertoken | pwd.password | * |
7 | usertoken | user | * |
8 | xireq | handler.type | java:com.sap.aii.axis.xi.XI30InboundHandler |
9 | xires | handler.type | java:com.sap.aii.axis.xi.XI30InboundHandler |
Header Payload :
<soapenv:Header>
<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope" soapenv:actor="www.toromont.com" soapenv:mustUnderstand="1">
<wsu:Timestamp xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<wsu:Created>2015-09-01T10:00:31Z</wsu:Created>
<wsu:Expires>2015-09-30T18:01:31Z</wsu:Expires>
</wsu:Timestamp>
<wsse:UsernameToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="UsernameToken-232">
<wsse:Username>***********</wsse:Username>
<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">**********</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
</soapenv:Header>
Regards,
Jannus Botha
Hi,
As anyone faced this problem before?
Regards,
Jannus Botha
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.