Last modified: 2014-11-17 10:19:47 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T72964, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 70964 - oauth plugin doesn't work in vagrant, seemingly due to the https reverse-proxy
oauth plugin doesn't work in vagrant, seemingly due to the https reverse-proxy
Status: NEW
Product: MediaWiki-Vagrant
Classification: Unclassified
General (Other open bugs)
unspecified
All All
: Low normal
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-09-17 22:01 UTC by Mukunda Modell
Modified: 2014-11-17 10:19 UTC (History)
4 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Mukunda Modell 2014-09-17 22:01:16 UTC
When attempting to test mediawiki oauth against a test instance of mediawiki vagrant, something is stripping the auth headers from the https request. I think it's related to the nginx reverse proxy but I couldn't find anything wrong with the nginx config or anything else that looked like an obvious problem.
Comment 1 Bryan Davis 2014-09-17 22:05:11 UTC
(In reply to Mukunda Modell from comment #0)
> ... related to the nginx reverse proxy ...

Which nginx reverse proxy? Could you describe your testing environment in more detail?
Comment 2 Mukunda Modell 2014-09-19 03:05:00 UTC
It's the standard mediawiki vagrant box, not customized in any significant way.

I'm referring to the proxy that sits between mediawiki and the world outside the VM connecting to the forwarded port 4430 for https.

This is set up by the puppet rules for the https role in mediawiki vagrant.
Comment 3 Mukunda Modell 2014-09-19 03:07:20 UTC
@bd808: I'm planning to test this further, just filed to bug to remind myself because it had slipped my mind for a while and I didn't want to forget it again.
Comment 4 Seb35 2014-11-17 10:19:47 UTC
See also bug 73510 related to the non-standard HTTPS port + reverse proxy. Possibly OAuth doesn’t like non-standard port and/or isn’t aware a non-standard port is used.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links