mahara-contributors team mailing list archive

[Mahara Bot <829674@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://reviews.mahara.org/631
Committed: http://gitorious.org/mahara/mahara/commit/2262a1a78b271998043288f6bfcf0c27c5797919
Submitter: Hugh Davenport (hugh@xxxxxxxxxxxxxxx)
Branch:    master

commit 2262a1a78b271998043288f6bfcf0c27c5797919
Author: Melissa Draper <melissa@xxxxxxxxxxxxxxx>
Date:   Thu Sep 1 14:48:05 2011 +1200

    Add configuration and init checks for SSL proxies (bug #829674)
    
    Currently use of a proxy such as nginx to force https usage results
    in a bit of loopiness. This patch adds the sslproxy setting and when
    this is set, mandates that the wwwroot be a https address.
    
    Change-Id: Ic4cfe048202cea60098e60e57adb99a0cb594619
    Signed-off-by: Melissa Draper <melissa@xxxxxxxxxxxxxxx>

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
https://bugs.launchpad.net/bugs/829674

Title:
  Add SSL reverse proxy support like ssl_proxy in Moodle

Status in Mahara ePortfolio:
  In Progress

Bug description:
  Mahara needs to have SSL reverse proxy support like Moodle does using
  ssl_proxy. All versions of Mahara are affected (we are on 1.4.1).

  The issue is that we are serving SSL certificates from a load
  balancer. This means the Mahara server thinks itself is http which
  causes it to generate a shared key with http://mahara.mysite.com in
  the header.

  This presents itself as a problem when trying to set up SSO with
  Moodle, since Moodle looks at Mahara's shared key, notices it's
  actually coming from a secure site (https) and says the key is
  incorrect.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/829674/+subscriptions