Closed
Bug 1443704
Opened 7 years ago
Closed 6 years ago
Users can provide credentials to see and land confidential revisions
Categories
(Conduit :: General, enhancement)
Conduit
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mcote, Assigned: zalun)
References
(Blocks 1 open bug)
Details
(Keywords: conduit-story, conduit-triaged)
Attachments
(1 file)
In order to both view and land confidential revisions, users must authenticate somehow to Phabricator.
Comment hidden (off-topic) |
Comment hidden (off-topic) |
Updated•7 years ago
|
Flags: needinfo?(smacleod)
Reporter | ||
Updated•7 years ago
|
Assignee: nobody → pzalewa
Status: NEW → ASSIGNED
Assignee | ||
Comment 3•7 years ago
|
||
The user is providing the Phabricator API Token manually in the Navbar modal.
The browser is storing its value in the cookie.
Lando UI backend is passing the token to the Lando API in request's header.
`PHABRICATOR_URL` config is added with a default value set to
`https://phabricator.services.mozilla.com/`.
Fixed Nits:
I've removed the `npm install` line. "no such command."
Please make sure this is not needed before accepting.
Assignee | ||
Updated•7 years ago
|
Group: conduit-security
Assignee | ||
Comment 4•7 years ago
|
||
Phabricator API endpoints require a token to authenticate the user.
Currently, we use a default unprivileged token for all the requests. It gives us access to public revisions.
To be able to view and land secure revisions, Lando needs to use a token generated by the Phabricator user.
Each user can generate multiple permanent API tokens.
A user authenticates in Phabricator using BMO Auth.
Lando UI will have a way for the authenticated (Auth0) user to provide the token (copy & paste using the browser). It would then store it and pass to the Lando API as the X-Phabricator-API-Key header in every request. The token should be removed from Lando onon user's demand or if the user is logged out. Reusing the same token next time is possible.
Storing the token in a session is not suitable for us (see discussion here [1])
One solution would be to store the token in a secure, HttpOnly cookie. The cookie will be deleted on log out.
Implementation would require sending the token to the server with a CSRF protected POST request.
[1] https://phabricator.services.mozilla.com/D2561#55271
Assignee | ||
Updated•7 years ago
|
Group: conduit-security
Updated•7 years ago
|
Attachment #8996279 -
Attachment description: WIP - landing: Add an ability to see and land secure revisions. → landing: Add an ability to see and land secure revisions.
Comment 5•7 years ago
|
||
Comment on attachment 8996279 [details]
landing: Add an ability to see and land secure revisions.
Israel Madueme [:imadueme] has approved the revision.
Attachment #8996279 -
Flags: review+
Comment 6•6 years ago
|
||
Comment on attachment 8996279 [details]
landing: Add an ability to see and land secure revisions.
Steven MacLeod [:smacleod] has approved the revision.
Attachment #8996279 -
Flags: review+
Comment 7•6 years ago
|
||
This has landed, should go out with the next deploy.
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•