Bug #5319
closed
Could the problem have something to do with the fact that the address is a .org rather than a commons URL?
- Status changed from New to Resolved
- Target version set to Not tracked
Sorta. It appears that the brooklynwaterfront.org domain itself is not actually hosted at the Commons. It's on a different IP (50.21.188.170). That server loads a webpage that contains nothing but an iframe, and the iframe contains the content of http://bwrc.commons.gc.cuny.edu/, which is hosted on the Commons. As such, brooklynwaterfront.org/wp-admin is not a real page. For security reasons, WordPress does not allow the Dashboard to be loaded inside of an iframe.
If the admin of brooklynwaterfront.org would like to be able to administer the site under brooklynwaterfront.org/wp-admin, the domain will have to be mapped to the Commons, as per our normal procedures. Otherwise, the Dashboard is accessible via https://bwrc.commons.gc.cuny.edu/wp-admin.
Whoa. Does this set-up present any security issues?
I don't think so. WordPress sends a same-origin header to the browser, which prevents the browser from accepting cookies from *.commons.gc.cuny.edu domains if the URL in the location bar doesn't match the *.commons.gc.cuny.edu policy. In other words, it's not possible to be logged into the Commons when the Commons is being shown in an iframe on a site with a non-Commons domain. This mitigates all the obvious security issues (cookie forgery, CSRF, etc).
- Status changed from Resolved to New
This site is having problems again. Can I be added as an admin? Thanks!
FYI, the site isn't loading at all for me
- Assignee changed from Boone Gorges to Marilyn Weber
- Status changed from New to Resolved
Going to close this one out again. If there continue to be iframe-related problems, even after fixing HTTPS issues, then the authors may want to consider working with our team to do a standard domain mapping setup.
- Related to Support #14850: brooklyn waterfront site "connection not secure" added
Also available in: Atom
PDF