Use SSL with Sharepoint protocol
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-28-2014 07:48 AM
Hi,
I followed some instructions to run the Sharepoint protcol with SSL on port 7070.
First changed vti-context.xml to use SSL, then added this to vti.properties:
vti.server.port=7070
vti.server.protocol=https
vti.server.ssl.keystore=/opt/alfresco-4.2.f/alf_data/keystore/ssl.keystore
vti.server.ssl.password=kT9X6oe68t
vti.server.url.path.prefix=/alfresco
vti.server.external.host=[hostname]
vti.server.external.port=7070
vti.server.external.protocol=https
vti.server.external.contextPath=/alfresco
Now I do get SSL, but as it is a self signed certificate I always get some warnings before I can open a document.
Also I see these info messages in catalina.out:
2014-04-28 13:36:38,268 INFO [vti.web.VtiRequestDispatcher] [1880889499@qtp-1454731198-0] Note - no handler was found for OPTIONS to uri='/zandbak/documentLibrary/'
2014-04-28 13:36:41,471 INFO [vti.web.VtiRequestDispatcher] [1880889499@qtp-1454731198-0] Note - no handler was found for HEAD to uri='/zandbak/documentLibrary/Zandbak.docx'
2014-04-28 13:36:44,200 INFO [vti.web.VtiRequestDispatcher] [780995441@qtp-1454731198-2] Note - no handler was found for GET to uri='/zandbak/documentLibrary/Zandbak.docx'
2014-04-28 13:36:53,006 INFO [vti.web.VtiRequestDispatcher] [780995441@qtp-1454731198-2] Note - no handler was found for GET to uri='/zandbak/documentLibrary/Zandbak.docx'
On this server I already installed a 3rd party certificate for Alfresco https traffic using the Apache mod.
Is it possible to use this 3rd party certificate for the Sharepoint protocol and how do I manage that?
Are the INFO messages in catalina.out important?
Thanks for your input.
Regards,
Frank
I followed some instructions to run the Sharepoint protcol with SSL on port 7070.
First changed vti-context.xml to use SSL, then added this to vti.properties:
vti.server.port=7070
vti.server.protocol=https
vti.server.ssl.keystore=/opt/alfresco-4.2.f/alf_data/keystore/ssl.keystore
vti.server.ssl.password=kT9X6oe68t
vti.server.url.path.prefix=/alfresco
vti.server.external.host=[hostname]
vti.server.external.port=7070
vti.server.external.protocol=https
vti.server.external.contextPath=/alfresco
Now I do get SSL, but as it is a self signed certificate I always get some warnings before I can open a document.
Also I see these info messages in catalina.out:
2014-04-28 13:36:38,268 INFO [vti.web.VtiRequestDispatcher] [1880889499@qtp-1454731198-0] Note - no handler was found for OPTIONS to uri='/zandbak/documentLibrary/'
2014-04-28 13:36:41,471 INFO [vti.web.VtiRequestDispatcher] [1880889499@qtp-1454731198-0] Note - no handler was found for HEAD to uri='/zandbak/documentLibrary/Zandbak.docx'
2014-04-28 13:36:44,200 INFO [vti.web.VtiRequestDispatcher] [780995441@qtp-1454731198-2] Note - no handler was found for GET to uri='/zandbak/documentLibrary/Zandbak.docx'
2014-04-28 13:36:53,006 INFO [vti.web.VtiRequestDispatcher] [780995441@qtp-1454731198-2] Note - no handler was found for GET to uri='/zandbak/documentLibrary/Zandbak.docx'
On this server I already installed a 3rd party certificate for Alfresco https traffic using the Apache mod.
Is it possible to use this 3rd party certificate for the Sharepoint protocol and how do I manage that?
Are the INFO messages in catalina.out important?
Thanks for your input.
Regards,
Frank
Labels:
- Labels:
-
Archive
11 REPLIES 11
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-13-2014 04:41 AM
I added headers_module modules/mod_headers.so to httpd.conf. Apache told me module was already there.
I changed vti-context.xml to your settings.
Realized that I didn't download jetty-ajp-6.1.14.jar. So I did.
For the Apache errors I enabled mod proxy_http.
Alfresco now starts perfectly without errors.
But when I try to edit a Word or Excel file online Office warns me that the file at port 1111 can be harmful. Then Word or Excel starts and finally I get a message that the file (https://servername.domain.com:1111/path_to_file/file) cannot be opened.
This is driving me nuts!!!
When I look at your explanation in the other post I skipped creating the tomcat connector. I already enabled SSL through mod_jk. I suppose the worker is also defined (if I look at my virtualhost:443).
Added virtualhost:1111 the way you explained.
No errors in catalina.out and this is what I find in the Apache error log:
[Tue May 13 10:34:11.276856 2014] [ssl:error] [pid 2849:tid 139913534048000] [client 10.0.1.111:17642] AH02261: Re-negotiation handshake failed: Not accepted by client!?, referer: https://alfresco.ourdomain.com/share/page/site/zandbak/document-details?nodeRef=workspace://SpacesSt...
[Tue May 13 10:34:11.430631 2014] [ssl:error] [pid 2849:tid 139913458513664] [client 10.0.1.111:17644] AH02261: Re-negotiation handshake failed: Not accepted by client!?, referer: https://alfresco.ourdomain.com/share/page/site/zandbak/document-details?nodeRef=workspace://SpacesSt...
[Tue May 13 10:34:11.434038 2014] [ssl:error] [pid 2849:tid 139913542440704] [client 10.0.1.111:17645] AH02261: Re-negotiation handshake failed: Not accepted by client!?, referer: https://alfresco.ourdomain.com/share/page/site/zandbak/document-details?nodeRef=workspace://SpacesSt...
[Tue May 13 10:34:11.436806 2014] [ssl:error] [pid 2849:tid 139913617975040] [client 10.0.1.111:17647] AH02261: Re-negotiation handshake failed: Not accepted by client!?, referer: https://alfresco.ourdomain.com/share/page/site/zandbak/document-details?nodeRef=workspace://SpacesSt...
[Tue May 13 10:34:11.461485 2014] [ssl:error] [pid 2849:tid 139913626367744] [client 10.0.1.111:17646] AH02261: Re-negotiation handshake failed: Not accepted by client!?, referer: https://alfresco.ourdomain.com/share/page/site/zandbak/document-details?nodeRef=workspace://SpacesSt...
[Tue May 13 10:34:14.559882 2014] [proxy:warn] [pid 2849:tid 139913643153152] [client 10.0.1.111:17654] AH01144: No protocol handler was valid for the URL /alfresco/zandbak/documentLibrary/. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule.
[Tue May 13 10:34:16.924618 2014] [proxy:warn] [pid 2849:tid 139913601189632] [client 10.0.1.111:17655] AH01144: No protocol handler was valid for the URL /alfresco/zandbak/documentLibrary/Zandbak.docx. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule.
[Tue May 13 10:34:16.952391 2014] [proxy:warn] [pid 2849:tid 139913559226112] [client 10.0.1.111:17656] AH01144: No protocol handler was valid for the URL /alfresco/zandbak/. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule.
[Tue May 13 10:34:17.053874 2014] [proxy:warn] [pid 2849:tid 139913576011520] [client 10.0.1.111:17657] AH01144: No protocol handler was valid for the URL /alfresco/zandbak/documentLibrary/Zandbak.docx. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule.
I changed vti-context.xml to your settings.
Realized that I didn't download jetty-ajp-6.1.14.jar. So I did.
For the Apache errors I enabled mod proxy_http.
Alfresco now starts perfectly without errors.
But when I try to edit a Word or Excel file online Office warns me that the file at port 1111 can be harmful. Then Word or Excel starts and finally I get a message that the file (https://servername.domain.com:1111/path_to_file/file) cannot be opened.
This is driving me nuts!!!
When I look at your explanation in the other post I skipped creating the tomcat connector. I already enabled SSL through mod_jk. I suppose the worker is also defined (if I look at my virtualhost:443).
Added virtualhost:1111 the way you explained.
No errors in catalina.out and this is what I find in the Apache error log:
[Tue May 13 10:34:11.276856 2014] [ssl:error] [pid 2849:tid 139913534048000] [client 10.0.1.111:17642] AH02261: Re-negotiation handshake failed: Not accepted by client!?, referer: https://alfresco.ourdomain.com/share/page/site/zandbak/document-details?nodeRef=workspace://SpacesSt...
[Tue May 13 10:34:11.430631 2014] [ssl:error] [pid 2849:tid 139913458513664] [client 10.0.1.111:17644] AH02261: Re-negotiation handshake failed: Not accepted by client!?, referer: https://alfresco.ourdomain.com/share/page/site/zandbak/document-details?nodeRef=workspace://SpacesSt...
[Tue May 13 10:34:11.434038 2014] [ssl:error] [pid 2849:tid 139913542440704] [client 10.0.1.111:17645] AH02261: Re-negotiation handshake failed: Not accepted by client!?, referer: https://alfresco.ourdomain.com/share/page/site/zandbak/document-details?nodeRef=workspace://SpacesSt...
[Tue May 13 10:34:11.436806 2014] [ssl:error] [pid 2849:tid 139913617975040] [client 10.0.1.111:17647] AH02261: Re-negotiation handshake failed: Not accepted by client!?, referer: https://alfresco.ourdomain.com/share/page/site/zandbak/document-details?nodeRef=workspace://SpacesSt...
[Tue May 13 10:34:11.461485 2014] [ssl:error] [pid 2849:tid 139913626367744] [client 10.0.1.111:17646] AH02261: Re-negotiation handshake failed: Not accepted by client!?, referer: https://alfresco.ourdomain.com/share/page/site/zandbak/document-details?nodeRef=workspace://SpacesSt...
[Tue May 13 10:34:14.559882 2014] [proxy:warn] [pid 2849:tid 139913643153152] [client 10.0.1.111:17654] AH01144: No protocol handler was valid for the URL /alfresco/zandbak/documentLibrary/. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule.
[Tue May 13 10:34:16.924618 2014] [proxy:warn] [pid 2849:tid 139913601189632] [client 10.0.1.111:17655] AH01144: No protocol handler was valid for the URL /alfresco/zandbak/documentLibrary/Zandbak.docx. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule.
[Tue May 13 10:34:16.952391 2014] [proxy:warn] [pid 2849:tid 139913559226112] [client 10.0.1.111:17656] AH01144: No protocol handler was valid for the URL /alfresco/zandbak/. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule.
[Tue May 13 10:34:17.053874 2014] [proxy:warn] [pid 2849:tid 139913576011520] [client 10.0.1.111:17657] AH01144: No protocol handler was valid for the URL /alfresco/zandbak/documentLibrary/Zandbak.docx. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-13-2014 04:54 PM
Do you have a firewall that maybe blocking the connection?
Also, I only used 1111 as the port number as an example; for my actual production I used a port number in the 7000 range. I'm not sure if that would have any bearing on it or not, but it could be worth a try. I also get the "this file might be harmful" blah blah blah…which we live with.
Another thing you can try is to upload a fresh document to Alfresco and then try online editing which should open up your office product.
**Edit**
I asked around on this and a suggestion was to install a2enmod headers and make sure they are enabled.
Also, I only used 1111 as the port number as an example; for my actual production I used a port number in the 7000 range. I'm not sure if that would have any bearing on it or not, but it could be worth a try. I also get the "this file might be harmful" blah blah blah…which we live with.
Another thing you can try is to upload a fresh document to Alfresco and then try online editing which should open up your office product.
**Edit**
I asked around on this and a suggestion was to install a2enmod headers and make sure they are enabled.
