cancel
Showing results for 
Search instead for 
Did you mean: 

Online editing without registry modifications

majykoyster
Champ in-the-making
Champ in-the-making
Hi there

I can edit MS Office files online, but to do so I had to modify registry entries (BasicAuthLevel=2) to allow Office to open files from the web, as explained in the help I found on the subject. It's ok for local users, but now I have to make Alfresco accessible to clients. Asking them to execute a .reg file to access documents is a no-no (so says my boss !), so I need to find another way.

I tried to set Tomcat to use SSL, since I think a secured connexion could solve the problem (maybe I'm wrong). Speaking of Tomcat, is the version bundled with Alfresco the "real deal", or is it a modified/truncated/simplified version ? I see lots of dead links on its home page, and since the countless how-to's I tried to use SSL all failed, I begin to wonder.

Thanks in advance for any input !
3 REPLIES 3

parzgnat
Star Contributor
Star Contributor
I believe that you're on the right track in that using the MS Office SharePoint protocol with Alfresco will be possible with no registry changes if you enable SSL.  I think the trick is that the the SharePoint protocol actually does not run on the Tomcat instance that Alfresco is running on.  It runs on a separate Jetty instance that gets launched when the Alfresco server starts up.  If you enable SSL on the Jetty instance you should be all set.

More information can be found here:
http://docs.alfresco.com/4.2/index.jsp?topic=%2Fcom.alfresco.enterprise.doc%2Ftasks%2FSharePoint-HTT...

I hope this helps.

majykoyster
Champ in-the-making
Champ in-the-making
Thanks for the input !

I'll check that in detail tomorrow, time to go home.

majykoyster
Champ in-the-making
Champ in-the-making
I followed each step of the procedure, now I get a "connection failed" on https://srv-alfresco:8433/share. Trying to connect to srv-alfresco:8080/share now generates about a million errors (maybe an expected behavior after the changes I made).

The keystore generation completed with no error, same with the certification file and the import of the certification into cacerts.

Here are the files I modified (don't mind the stupid passwords, it's only a test server).

Any input welcome !

edit : forgot the log file.


vti-context.xml

 104    <bean id="vtiServerConnector" class="org.mortbay.jetty.security.SslSocketConnector">
105         <property name="port">
106              <value>${vti.server.port}</value>
107         </property>
108         <property name="headerBufferSize">
109              <value>8192</value>
110         </property>
111         <property name="maxIdleTime">
112              <value>30000</value>
113         </property>
114         <property name="keystore">
115              <value>/opt/alfresco-4.2.0/alf_data/keystore/labstore.jks</value>
116         </property>
117         <property name="keyPassword">
118              <value>P@ssword</value>
119         </property>
120         <property name="password">
121              <value>P@ssword</value>
122         </property>
123         <property name="keystoreType">
124              <value>JKS</value>
125         </property>
126     </bean>



server.xml

 85     <Connector port="8443" URIEncoding="UTF-8" protocol="HTTP/1.1" SSLEnabled="true"
86                maxThreads="200" scheme="https" secure="true"
87                keystoreFile="/opt/alfresco-4.2.0/alf_data/keystore/labstore.jks"
88                keystorePass="P@ssword"
89                clientAuth="false" sslProtocol="TLS" maxHttpHeaderSize="32768" />



share-config-custom.xml

The "activiti-admin" endpoint wasn't mentioned in the Alfresco documentation. I tried to keep it how it was then to modify it with https/8443, didn't change a thing.

321    <config evaluator="string-compare" condition="Remote">
322       <remote>
323          <endpoint>
324             <id>alfresco-noauth</id>
325             <name>Alfresco - unauthenticated access</name>
326             <description>Access to Alfresco Repository WebScripts that do not require authentication</description>
327             <connector-id>alfresco</connector-id>
328             <endpoint-url>https://localhost:8443/alfresco/s</endpoint-url>
329             <identity>none</identity>
330          </endpoint>
331
332          <endpoint>
333             <id>alfresco</id>
334             <name>Alfresco - user access</name>
335             <description>Access to Alfresco Repository WebScripts that require user authentication</description>
336             <connector-id>alfresco</connector-id>
337             <endpoint-url>https://localhost:8443/alfresco/s</endpoint-url>
338             <identity>user</identity>
339          </endpoint>
340
341          <endpoint>
342             <id>alfresco-feed</id>
343             <name>Alfresco Feed</name>
344             <description>Alfresco Feed - supports basic HTTP authentication via the EndPointProxyServlet</description>
345             <connector-id>http</connector-id>
346             <endpoint-url>https://localhost:8443/alfresco/s</endpoint-url>
347             <basic-auth>true</basic-auth>
348             <identity>user</identity>
349          </endpoint>
350
351          <endpoint>
352             <id>activiti-admin</id>
353             <name>Activiti Admin UI - user access</name>
354             <description>Access to Activiti Admin UI, that requires user authentic    ation</description>
355             <connector-id>activiti-admin-connector</connector-id>
356             <endpoint-url>https://localhost:8443/alfresco/activiti-admin</endpoint-url>
357             <identity>user</identity>
358          </endpoint>
359       </remote>
360    </config>