Hi Tobias, thank you for your quick answer.
> from what I see you are mixing two different approaches for SSL. The first > one is to have Apache serve up SSL and leave Matterhorn running on plain > HTTP. This is when you need the X-Forwarded-SSL header (note that is a very > recent fix for SSL related problems, so you current installation - until > updated during the course of the last week - will most probaly not support it. > > The other option (which you seem to be following at the same time) is have > Matterhorn on SSL. This is when you need to import the SSL certificate into > the java keystore. > > If I were you, and you don't have reasons to do otherwise, I would suggest to > stick with Apache running SSL and Matterhorn running HTTP. Currently, I am running Matterhorn 1.3.1 and I would like to run Apache with HTTPS and Matterhorn on plain HTTP as you suggested. I saw that it is possible to configure Matterhorn to run on HTTPS, but that's not what I wanted. Therefore I left org.osgi.service.http.port=8080 and org.osgi.service.http.secure.enabled=false on the default settings in config.properties. What I didn't understand until now: I did change all URLs in config.properties to "https://...."; without Port 8080 to make the Matterhorn web frontend run via HTTPS, this is working well with my configuration. What communication channel is Matterhorn using internally now, still HTTP over 8080 or HTTPS over 443? Furthermore, I only added the certificates to the truststore to make Matterhorn communicate internally with my self-signed certificates. Without the truststore, it didn't work either. Tobias, could you please give me a hint what I am doing wrong, what I should do or what I should leave to get it running? Thanks in advance, Best regards Alexander Bias University of Ulm kiz information systems
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Matterhorn-users mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
