Selecting authData doesn't work

[rihadavid]

Issue Description

When querying _User and selecting authData, it's not contained in the response. The workaround is to select _auth_data_facebook instead. But authData should also work.

Steps to reproduce

Try in the API console, for example where={"username":"youruser"}&keys=authData vs where={"username":"youruser"}&keys=_auth_data_facebook

• Server

  • parse-server version: tested on 2.3.3, 2.8.4, 3.1.2

• Database

  • MongoDB version: 3.6.6, mlab
  • Localhost or remote server? Both local and SashiDo

[acinader]

are you using the masterkey?

parse-server/src/RestQuery.js

Lines 854 to 856 in 46ac7e7

	if (obj.className == '_User' && !auth.isMaster) {
	delete obj.sessionToken;
	delete obj.authData;

[rihadavid]

yes I am

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[rihadavid]

Someone should probably look at this easily reproducible bug and try it on the latest version before the stalebot will close it 😉
@dplewis maybe?

[dplewis]

Have you tried with Javascript SDK?

user->get('authData');

[rihadavid]

I'm not sure, it's been two months since I was dealing with this issue. Just wanted to notify you about this issue before it gets closed because it's clearly a bug. Unfortunately, I don't currently have time to investigate deeper, hopefully, someone will 🤔

[dplewis]

I’ve been using authData a lot recently and this should work. I’ll look into REST API.

[dplewis]

@rihadavid The answer you want is here. https://github.com/parse-community/parse-server/pull/2081/files#r67542317

[rihadavid]

@dplewis I am sorry, what do you mean? An answer to what? 🤔 Were you able to try to reproduce the issue by the steps I provided, in the API console?

[mtrezza]

The issue may be because the field authData does not actually exist in the DB, it is synthesized from the _auth_data_* fields in the DB, so a reference to authData does not work in all cases.

See a similar issue where Parse Server does not interpret a reference as expected in this forum thread.

Fixing this is probably pretty simple.