mahara-contributors team mailing list archive

[Mahara Bot <829674@xxxxxxxxxxxxxxxxxx>]

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

commit aff1ab49ebcef630561441468f590745e01bc601
Author: Melissa Draper <melissa@xxxxxxxxxxxxxxx>
Date:   Fri Sep 9 13:22:55 2011 +1200

    Add default sslproxy configuration (bug #829674)
    
    This was missing and the error logs were being polluted as a result.
    
    Change-Id: I80e6315d25fd1ccb71e37e77f7922784ec3d72ed
    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