HTTPS

[omegerard]

Hi

I don't know whether it was somewhere in the documentation, but I thought that https delivery was being implemented.

This is one of the key requirements for a pilot implementation at our site.

When could this feature be expected?

Regards

Ludo

[kevinr]

Hello,

We have tried the server using HTTPS and it works now. It requires you to configure you app-server (E.g. TomCat) correctly but it has been tested and appears to work ok. Please let us know how you get on with this.

Thanks,

Kevin

[steve]

Hello,

To add to what Kevin added, I've been performing my testing in HTTPS, on both Tomcat and Jboss since our first preview release.
To see how to configure Tomcat for SSL have a look in the Tomcat 'server.xml' file and follow the instructions in there.

Steve

[omegerard]

Kevin, Steve

Thank you for your help.

Works pretty much out of the box.

I am impressed. Once again.

Regards

Ludo

[steve]

No problems,
Glad we could help…

Steve

[markthompson23]

I have been trying to get the site up using SSL but I'm running into some problems.

I followed the instructions on the apache/tomcat site for creating a certificate and a keystore.  I modified the 'server.xml' accordingly.

I cannot get to alfresco by using either http://localhost:8443/alfresco or https://localhost:8443/alfresco.  I can get to the root site page using http://localhost:8443/.

Are there any changes required to Alfresco either in the config files or in setting up the directory structure?

[markthompson23]

I resolved my problem.  It was related to the keystore.

I now have the site running under SSL.

[schlagobert]

@markthompson23

i have the same problem: how did you resolve it? how is this related to the keystore?

best regards,
stefan

[piman31415]

I was (mostly) able to get SSL working by using proxy settings in the Apache ssl version of the httpd configuration file (located in the file /etc/httpd/conf.d/ssl.conf on a standard Fedora Core 6 installation). 

However, if a user is not already logged in, and a user requests a page somewhere "deep" in the folder hierarchy with an https:// header, the user is redirected to the login page which is presented as a non-ssl page (http:// header).  All subsequent pages are also then delivered non-ssl.  If a user has already logged in and manually sets an https://.../alfresco/… page, all subsequent links maintain the https prefix.  Has anyone else experienced this, and if so, can you report a work-around?

Thanks!