Public bug reported: 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. ** Affects: mahara Importance: Undecided Status: New ** Tags: mahoodle proxy ssl sso -- You received this bug notification because you are a member of Mahara Core, 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: New 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 _______________________________________________ Mailing list: https://launchpad.net/~mahara-core Post to : [email protected] Unsubscribe : https://launchpad.net/~mahara-core More help : https://help.launchpad.net/ListHelp
