parse-community / parse-community/parse-dashboard

User field `authData` cannot be deleted

Open
#1,957 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type:bug
Dominant language
JavaScript
Stars
3.8k
Forks
1.4k
PR merge metrics
No merged PRs in 30d

Description

New Issue Checklist
Issue Description

Trying to delete the authData field in the _User collection fails with error:

This authentication method is unsupported.

Steps to reproduce
  1. Find user with a populated authData field
  2. Select cell
  3. Hit delete button
Actual Outcome

Error message appears, field value is not deleted.

Expected Outcome

Field value should be deleted.

Note

It also does not work to only select a specific auth provider in the authData field and delete on that provider entry, e.g. "facebook: { ... }" or "apple: { ... }". The result appears correctly in the cell with the authData field updated to {}, even showing a success pop-up. But after refreshing the data browser, the auth data is still there.

Environment

Dashboard

  • Parse Dashboard version: 3.2.1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in the Data Browser by reproducing deletion of the _User authData field and compare deleting the whole field with deleting a provider entry such as facebook or apple. Verify the fix against the reported error, the refreshed cell value, and the Parse Dashboard 3.2.1 behavior described in the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.