Skip to content

runAsUser(user) does not propagate sessionToken for .first(), .aggregate(), and some query paths, causing 101 "Permission denied" on CLP classes in cloud functions #272

Description

@sadortun

Problem

When using Query.create(Class).runAsUser(user) from @goplan-finance/utils inside a Parse Cloud Function (defined with requireUser: false), the session token is not reliably applied to all query execution methods.

This causes:

{"code": 101, "error": "Permission denied, user needs to be authenticated."}

Even when:
• request.user is a valid authenticated user with a session token
• The UI called Parse.Cloud.run(...) with a logged-in user
• The class has requiresAuthentication in its CLP for find/get

Observed Behavior

• .find() after runAsUser() usually works (token is injected).
• .first(), direct .get(), and .aggregate() frequently do not.

From @goplan-finance/utils@1.1.3:

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions