<?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: Web Services over https (SSL) in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/web-services-over-https-ssl/m-p/257236#M210366</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Thank you. Your suggestions pointed us in the right direction and now everything is working. Everything had to do with the WS-Security SOAP header for the UsernameToken as you indicated.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 09 Nov 2011 20:34:03 GMT</pubDate>
    <dc:creator>lcjr2002</dc:creator>
    <dc:date>2011-11-09T20:34:03Z</dc:date>
    <item>
      <title>Web Services over https (SSL)</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/web-services-over-https-ssl/m-p/257234#M210364</link>
      <description>We are using the Alfresco Community edition 4 and we really like all the functionality that Alfresco brings. We are considering moving to the paid version of Alfresco. However, we have run into an issue that is a definite deal breaker. Our team (we are all developers) is having a very difficult time</description>
      <pubDate>Fri, 28 Oct 2011 16:57:45 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/web-services-over-https-ssl/m-p/257234#M210364</guid>
      <dc:creator>lcjr2002</dc:creator>
      <dc:date>2011-10-28T16:57:45Z</dc:date>
    </item>
    <item>
      <title>Re: Web Services over https (SSL)</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/web-services-over-https-ssl/m-p/257235#M210365</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Have you tried to use the same C# implementation using HTTP?&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I suggest to test it on HTTP and then try to use HTTPS.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If you have problems using HTTP then it means that probably you have to implement the WS-Security SOAP header for the UsernameToken that must be coded by yourself in order to work on Alfresco, as any other Web Services applications:&lt;/SPAN&gt;&lt;BR /&gt;&lt;A href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wss" rel="nofollow noopener noreferrer"&gt;http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wss&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Alfresco provides a complete Java Web Service client that it could be used to take a look at the code and then try to understand how to set the UsernameToken in C# converting the code from Java to C#.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Hope this helps.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 Oct 2011 13:21:35 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/web-services-over-https-ssl/m-p/257235#M210365</guid>
      <dc:creator>openpj</dc:creator>
      <dc:date>2011-10-31T13:21:35Z</dc:date>
    </item>
    <item>
      <title>Re: Web Services over https (SSL)</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/web-services-over-https-ssl/m-p/257236#M210366</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Thank you. Your suggestions pointed us in the right direction and now everything is working. Everything had to do with the WS-Security SOAP header for the UsernameToken as you indicated.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Nov 2011 20:34:03 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/web-services-over-https-ssl/m-p/257236#M210366</guid>
      <dc:creator>lcjr2002</dc:creator>
      <dc:date>2011-11-09T20:34:03Z</dc:date>
    </item>
  </channel>
</rss>

