[Very much a longer-term enhancement.]
Parsoid doesn't currently have support for passing on an authenticated user's read right when fetching the wikitext (because the API doesn't support that yet).
Version: unspecified
Severity: enhancement
Description
Description
Details
Details
- Reference
- bz44483
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | • GWicke | T46483 Parsoid should support passing on an authenticated user's read right (when MW API supports that) | |||
| Declined | None | T14251 Read restriction support | |||
| Resolved | • csteipp | T32348 Add Oauth support to Mediawiki | |||
| Resolved | aaron | T55956 UX rework of MWOAuth/authorize | |||
| Resolved | None | T53221 Deprecated logging used in OAuth extension |
Event Timeline
Comment Actions
Passing on the cookie header from the VisualEditor extension to Parsoid and then from Parsoid back to the API might be enough to enable this. Definitely worth a try.
Comment Actions
Change 85414 had a related patch set uploaded by GWicke:
WIP Bug 44483: Forward Cookie header to API
Comment Actions
Random idea:
Could Parsoid be made private (already is, though last I checked it still has a public IP) and use an internal API instead of the public API. Then the responsibility for user rights lays in MediaWiki land, and when the request is in Parsoid we can assume it is authenticated and thus Parsoid can have unrestricted access.
Comment Actions
(In reply to comment #4)
Random idea:
Could Parsoid be made private (already is, though last I checked it still
has a
public IP) and use an internal API instead of the public API. Then the
responsibility for user rights lays in MediaWiki land, and when the request
is
in Parsoid we can assume it is authenticated and thus Parsoid can have
unrestricted access.
That is what we'll have to do in the longer term once we store HTML. Parsoid might not even be involved in that case, only the content API / storage is. See https://www.mediawiki.org/wiki/User:GWicke/Notes/Storage for the current WIP on that.
Comment Actions
Cookies are now forwarded, and caching is disabled if a cookie is set. Closing this bug as fixed. A content API will have to do its own auth.
Comment Actions
Change 91111 had a related patch set uploaded by Jforrester:
Support private wikis by forwarding Cookie: headers to Parsoid
Comment Actions
Change 91111 merged by jenkins-bot:
Support private wikis by forwarding Cookie: headers to Parsoid