Add afterFind to auth adapter

[dblythy]

New Feature / Enhancement Checklist

• I am not disclosing a vulnerability.
• I am not just asking a question.
• I have searched through existing issues.

Current Limitation

Currently, to strip authData fields, it needs to be done in an afterFind trigger

Feature / Enhancement Description

Give authAdapters the ability to customize find response

Example Use Case

Alternatives / Workarounds

3rd Party References

[parse-github-assistant]

Thanks for opening this issue!

• 🎉 We are excited about your ideas for improvement!

[mtrezza]

Could you give more details about the issue? In what scenario would one want to strip authData fields and from what should they be stripped?

[dblythy]

For the MFA Adapter, the secret which is used to generate the OTP is only meant to be seen on the server side.

[cbaker6]

Not sure if this can end up causing issues, but be mindful that most of the handling of authData happens on the client SDKs or on the client directly if a developer is using REST. See my comments in the following threads: #7737 (comment)

parse-community/Parse-SDK-JS#1353 (comment)

[dblythy]

Yeah, I don’t see it being implemented on many with adapters, but for the MFA one we need to store a secret in auth data which shouldn’t be seen on the client side. The client SDKs already need work to support the new auth adapters

[dblythy]

Related: https://community.parseplatform.org/t/remove-sensitive-data-from-authdata/2377/2

[parseplatformorg]

🎉 This change has been released in version 6.1.0-alpha.3

[parseplatformorg]

🎉 This change has been released in version 6.1.0-beta.2

[parseplatformorg]

🎉 This change has been released in version 6.1.0