Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pairing session with installation when using GraphQL #7699

Open
3 tasks done
azlekov opened this issue Nov 13, 2021 · 2 comments
Open
3 tasks done

Pairing session with installation when using GraphQL #7699

azlekov opened this issue Nov 13, 2021 · 2 comments
Labels
type:feature New feature or improvement of existing feature

Comments

@azlekov
Copy link

azlekov commented Nov 13, 2021

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 respect x-parse-installation-id header.
Example 2: login, signUp respecting x-parse-installation-id header

Alternatives / Workarounds

  1. creating and saving an installation
  2. creating a session using login, signUp etc.
  3. update session's installationId

3rd Party References

@parse-github-assistant
Copy link

Thanks for opening this issue!

  • 🎉 We are excited about your ideas for improvement!

@mtrezza
Copy link
Member

mtrezza commented Nov 14, 2021

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 #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 parse-community/docs#846 which should remove references to "restricted session".

@mtrezza mtrezza added type:feature New feature or improvement of existing feature and removed type:improvement labels Dec 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:feature New feature or improvement of existing feature
Projects
None yet
Development

No branches or pull requests

2 participants