Closed
Bug 679502
Opened 14 years ago
Closed 14 years ago
Updating storage to use the request.user object
Categories
(Cloud Services Graveyard :: Server: Sync, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: telliott, Unassigned)
Details
(Whiteboard: [qa+])
Attachments
(1 file)
|
4.93 KB,
patch
|
tarek
:
review+
|
Details | Diff | Splinter Review |
This one is pretty minor, but moves storage over to make use of the new request.user object.
Initially I thought this was essential for migration from /auth to /user, but I realize now that it isn't, as both are getting written into the space that storage is reading from, and it doesn't do anything more complicated.
Attachment #553589 -
Flags: review?(tarek)
|
||
Updated•14 years ago
|
Attachment #553589 -
Flags: review?(tarek) → review+
|
Reporter | |
Comment 1•14 years ago
|
||
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
|
|
||
Comment 2•14 years ago
|
||
QA needs steps to verify authentication backend, various scenarios...
Whiteboard: [qa+]
|
||
Updated•2 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•