<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: 4.0.d vs 4.2.d SOAP exception in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/4-0-d-vs-4-2-d-soap-exception/m-p/290668#M243798</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;After some poking with SoapUI I determined that 4.0.d was very forgiving of the timestamps in the security header.&amp;nbsp; 4.0.d was validating the timestamp format but not the values.&amp;nbsp; So it would accept timestamps 24 hours in the future for created and 25 hours in the future for expires.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;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.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;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.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 24 Sep 2013 23:17:55 GMT</pubDate>
    <dc:creator>bopolissimus</dc:creator>
    <dc:date>2013-09-24T23:17:55Z</dc:date>
    <item>
      <title>4.0.d vs 4.2.d SOAP exception</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/4-0-d-vs-4-2-d-soap-exception/m-p/290667#M243797</link>
      <description>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</description>
      <pubDate>Sun, 22 Sep 2013 23:38:23 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/4-0-d-vs-4-2-d-soap-exception/m-p/290667#M243797</guid>
      <dc:creator>bopolissimus</dc:creator>
      <dc:date>2013-09-22T23:38:23Z</dc:date>
    </item>
    <item>
      <title>Re: 4.0.d vs 4.2.d SOAP exception</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/4-0-d-vs-4-2-d-soap-exception/m-p/290668#M243798</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;After some poking with SoapUI I determined that 4.0.d was very forgiving of the timestamps in the security header.&amp;nbsp; 4.0.d was validating the timestamp format but not the values.&amp;nbsp; So it would accept timestamps 24 hours in the future for created and 25 hours in the future for expires.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;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.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;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.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 24 Sep 2013 23:17:55 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/4-0-d-vs-4-2-d-soap-exception/m-p/290668#M243798</guid>
      <dc:creator>bopolissimus</dc:creator>
      <dc:date>2013-09-24T23:17:55Z</dc:date>
    </item>
  </channel>
</rss>

