topic 4.0.d vs 4.2.d SOAP exception in Alfresco Archive https://connect.hyland.com/t5/alfresco-archive/4-0-d-vs-4-2-d-soap-exception/m-p/290667#M243797 <HTML><HEAD></HEAD><BODY><SPAN>Hi all,</SPAN><BR /><BR /><SPAN>I am running:</SPAN><BR /><BR /><SPAN>1. Alfresco 4.0.d bundle </SPAN><BR /><SPAN>2. Alfresco 4.2.d running on Ubuntu Precise LTE and distribution Tomcat7 and OpenJDK7</SPAN><BR /><SPAN>3. both alfresco instances talk to a distribution postgres 9.1 instance.</SPAN><BR /><SPAN>4. Moodle and Alfresco servers (test and production) are in the Australia/Melbourne timezone.</SPAN><BR /><BR /><SPAN>We have an Alfresco CE 4.0.d instance which is accessed by the moodle plugin via the SOAP interface.&nbsp; That works (in the sense that moodle is able to access files on Alfresco, read/update/create).</SPAN><BR /><BR /><SPAN>Recently (in prep for prod upgrade) I upgraded the testing instance to Alfresco CE 4.2.d (via 4.0.e for the activiti schema upgrades).&nbsp; Moodle accessing 4.2.d via the SOAP interface no longer works correctly.</SPAN><BR /><BR /><SPAN>After some investigation I see that:</SPAN><BR /><SPAN>&nbsp; 1. Moodle is sending a SOAP request where the created and expires timestamps are 12 hours ahead </SPAN><BR /><SPAN>&nbsp;&nbsp;&nbsp;&nbsp; of current time.</SPAN><BR /><BR /><PRE class="language-none line-numbers"><CODE><BR />&nbsp; &lt;Timestamp xmlns="<A href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" rel="nofollow noopener noreferrer">http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd</A>"&gt;<BR />&nbsp;&nbsp;&nbsp; &lt;Created&gt;<BR />2013-09-21T14:37:59Z&nbsp;&nbsp;&nbsp; &lt;/Created&gt;<BR />&nbsp;&nbsp;&nbsp; &lt;Expires&gt;<BR />2013-09-21T15:37:59Z&nbsp;&nbsp;&nbsp; &lt;/Expires&gt;<BR />&nbsp;&nbsp; &lt;/Timestamp&gt;<BR /><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN></CODE></PRE><BR /><BR /><SPAN>&nbsp; 2. Strange as the above seems, it *works* with Alfresco 4.0.d.&nbsp; I'm not sure why that (the</SPAN><BR /><SPAN>&nbsp;&nbsp;&nbsp;&nbsp; advancing of the time) is, perhaps something to do with the fact that Melbourne time </SPAN><BR /><SPAN>&nbsp;&nbsp;&nbsp;&nbsp; is halfway around the world from Greenwich (I've had to do a similar adjustment to </SPAN><BR /><SPAN>&nbsp;&nbsp;&nbsp;&nbsp; LDAP's personDifferentialQuery (see the +1300 below, although this was for Auckland </SPAN><BR /><SPAN>&nbsp;&nbsp;&nbsp;&nbsp; time but the reference I saw that suggested this was by someone in Sydney, I think, </SPAN><BR /><SPAN>&nbsp;&nbsp;&nbsp;&nbsp; so it may be a general timezone issue when around the world from GMT).</SPAN><BR /><BR /><A href="http://forums.alfresco.com/forum/installation-upgrades-configuration-integration/configuration/timezone-issue-ldap-differential" rel="nofollow noopener noreferrer">http://forums.alfresco.com/forum/installation-upgrades-configuration-integration/configuration/timezone-issue-ldap-differential</A><BR /><BR /><SPAN>&nbsp;&nbsp;&nbsp;&nbsp; and my adjustment was:</SPAN><BR /><BR /><PRE class="language-none line-numbers"><CODE><BR />&nbsp;&nbsp;&nbsp;&nbsp; ldap.synchronization.personDifferentialQuery=(&amp;(objectclass\=inetOrgPerson)(!(modifyTimestamp&lt;\={0}+1300)))<BR /><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN></CODE></PRE><BR /><BR /><SPAN>&nbsp; 3. When I switch over to alfresco 4.2.d on the test server, it receives the same advanced</SPAN><BR /><SPAN>&nbsp;&nbsp;&nbsp;&nbsp; timestamps as above, but that then fails with:</SPAN><BR /><BR /><PRE class="language-none line-numbers"><CODE><BR />AxisFault<BR /> faultCode: {<A href="http://schemas.xmlsoap.org/soap/envelope/}Server.generalException" rel="nofollow noopener noreferrer">http://schemas.xmlsoap.org/soap/envelope/}Server.generalException</A><BR /> faultSubcode:<BR /> faultString: WSDoAllReceiver: The timestamp could not be validated<BR /> faultActor:<BR /> faultNode:<BR /> faultDetail:<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; {<A href="http://xml.apache.org/axis/}stackTrace:WSDoAllReceiver" rel="nofollow noopener noreferrer">http://xml.apache.org/axis/}stackTrace:WSDoAllReceiver</A>: The timestamp could not be validated<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at org.apache.ws.axis.security.WSDoAllReceiver.invoke(WSDoAllReceiver.java:318)<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:454)<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281)<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:699)<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at javax.servlet.http.HttpServlet.service(HttpServlet.java:641)<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at org.alfresco.web.app.servlet.GlobalLocalizationFilter.doFilter(GlobalLocalizationFilter.java:61)<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:224)<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:169)<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927)<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:987)<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:579)<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:307)<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at java.lang.Thread.run(Thread.java:724)<BR /><BR /><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN></CODE></PRE><BR /><BR /><SPAN>Has anyone seen this? (with 4.2.b, 4.2.c, 4.2.d?)&nbsp; The servers have the same timezones and system time, so it's not likely that that's the issue.&nbsp; They *are* VMWare machines, so I've also done this test after setting their times to the same value (avoid issues with VMWare clock skew).</SPAN><BR /><BR /><SPAN>Thank you very much for any assistance.</SPAN><BR /><BR /><SPAN>Gerald</SPAN></BODY></HTML> Sun, 22 Sep 2013 23:38:23 GMT bopolissimus 2013-09-22T23:38:23Z 4.0.d vs 4.2.d SOAP exception https://connect.hyland.com/t5/alfresco-archive/4-0-d-vs-4-2-d-soap-exception/m-p/290667#M243797 Hi all,I am running:1. Alfresco 4.0.d bundle 2. Alfresco 4.2.d running on Ubuntu Precise LTE and distribution Tomcat7 and OpenJDK73. both alfresco instances talk to a distribution postgres 9.1 instance.4. Moodle and Alfresco servers (test and production) are in the Australia/Melbourne timezone.We ha Sun, 22 Sep 2013 23:38:23 GMT https://connect.hyland.com/t5/alfresco-archive/4-0-d-vs-4-2-d-soap-exception/m-p/290667#M243797 bopolissimus 2013-09-22T23:38:23Z Re: 4.0.d vs 4.2.d SOAP exception https://connect.hyland.com/t5/alfresco-archive/4-0-d-vs-4-2-d-soap-exception/m-p/290668#M243798 <HTML><HEAD></HEAD><BODY><SPAN>After some poking with SoapUI I determined that 4.0.d was very forgiving of the timestamps in the security header.&nbsp; 4.0.d was validating the timestamp format but not the values.&nbsp; So it would accept timestamps 24 hours in the future for created and 25 hours in the future for expires.</SPAN><BR /><BR /><SPAN>4.2.d does validate the timestamp against the time on the alfresco server (converted to GMT) so the moodle plugin's naive time adjustments don't work.</SPAN><BR /><BR /><SPAN>Solution is to sync the moodle and alfresco servers to NTP, remove the moodle plugin's +24 and +25 hour adjustments (adjust expires to 1 hour ahead or other acceptable interval) and have the moodle plugin convert the localtime to GMT correctly.</SPAN></BODY></HTML> Tue, 24 Sep 2013 23:17:55 GMT https://connect.hyland.com/t5/alfresco-archive/4-0-d-vs-4-2-d-soap-exception/m-p/290668#M243798 bopolissimus 2013-09-24T23:17:55Z