Closed Bug 1035297 Opened 10 years ago Closed 10 years ago

Device FMD lock code override

Categories

(Firefox OS Graveyard :: FindMyDevice, defect)

Product:
Firefox OS Graveyard
Component:
FindMyDevice
Platform:
x86_64
Windows 7
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX
Milestone:
2.0 S6 (18july)

People

(Reporter: jrconlin, Unassigned)

References

Details

A bug in the FirefoxOS lock screen system retains the previously set lock code, even after the lock code has been "deleted" from the device. As an interim fix, the server should be able to provide a lock code that will overwrite the existing device lock code. The new lock code would be sent as part of the lock request. 

Implementation of this fix depends on if the FMD client can successfully overwrite a previously set device lock code.
Hasn't it historically overrode previously set passcodes? I thought that a recent patch made the change that it doesn't.
Target Milestone: --- → 2.0 S6 (18july)
Blocks: 1034176
see related https://bugzil.la/1017263

Talking with ggp, we require the user to provide a passcode via the lock request if the device reports has_passcode:false. In this situation, the device will override any previously entered and now disabled passcode with the newly entered passcode. In essence, we treat it as if this is the first time a passcode is being set on the device. 

I don't believe it's possible to remotely lock the phone without a passcode, if so, this would be a server/WebUI bug to force users to provide a valid passcode before sending a lock request to the device.
Flags: needinfo?(vkrishnamoorthy)
Summary of our discussions regarding Passcode and the user experience is as follows.

1. When the user locks the device from the website remotely, the user will be prompted to create a new passcode. This passcode will over write the existing passcode if any on the device.
2. If the user performs "multiple lock device actions", the most recent passcode will be retained.

JR: GGP: do we need additional bugs for the server side as well as the website? We will need UX for the website to reflect this change.

elan: can we nom this for 2.0?
Flags: needinfo?(vkrishnamoorthy) → needinfo?(elancaster)
blocking-b2g: --- → 2.0?
Flags: needinfo?(elancaster)
Landed optional config setting to force passcode check to "false". This will allow webui to always send a lock code with the lock command:
https://github.com/mozilla-services/FindMyDevice/issues/210
Resolving this as Wont Fix as the good guys in the lockscreen team have fixed their bug (1034183) and uplifted it to 2.0
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
blocking-b2g: 2.0? → ---
You need to log in before you can comment on or make changes to this bug.