Open azlekov opened 2 years ago
The docs relate the endpoint to IoT applications:
IoT device calls the following endpoint to associate the its installationId with its session. This endpoint only works with session tokens from restricted sessions. Please note that REST API calls from an IoT device should use the Client Key, not the REST API Key.
In fact, we have removed the "restricted session" artifacts a while ago in https://github.com/parse-community/parse-server/pull/7543, so I am not sure how that endpoint behaves or whether the described scenario from the docs is still applicable. There is also an open issue https://github.com/parse-community/docs/issues/846 which should remove references to "restricted session".
New Feature / Enhancement Checklist
Current Limitation
The REST API have an option to pair session with installation but it looks like there's no alternative out of box for the GraphQL.
Feature / Enhancement Description
It would be great if there's similar API using the GraphQL and out of the box pair session with installation on the Parse Server. If is out of the box feature this will eliminate the need to do some calls using master key as the session or the installation permissions can differ.
If there's chance the GraphQL API to respect
x-parse-installation-id
will be great.Example Use Case
Example 1:
me
GraphQL query or mutation which respectx-parse-installation-id
header. Example 2: login, signUp respectingx-parse-installation-id
headerAlternatives / Workarounds
3rd Party References