-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Client Key Issues #159
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
Client Key Issues #159
Comments
This is how I initiate my JS Client and it seems to work for JS and iOS
Make sure you're using the javascriptKey, not the clientKey for JS https://parse.com/docs/js/api/classes/Parse.html#methods_initialize |
The best option is to not set any client keys in parse-server. They are not necessary and do not increase security. The issue here is that if you define any client keys (rest, client, js) then all requests must provide a valid key. So, if you had defined a client key, but not a Javascript key, that's why your JS calls failed. |
Thanks for the tip. I've initialized my parse server without a client key. Because one is required in the iOS SDK, I've just initialized it as 'unused':
Everything seems to be working fine. Appreciate the feedback! |
👍 |
I am having issues logging to the my version of the todoapp. below is the change i have made from Parse.initialize code block |
I'm currently working with two clients: JavaScript and an iOS app.
The JavaScript client will only connect if I don't have a client key defined upon setup:
The initialization and query of Parse in my Javascript is:
If I include the client key in the initialization of the parse server and my query -- I get a 403 (authorization error).
The iOS SDK requires the clientKey upon initialization or else it will not build. Because of this, I'm not able to connect both of my clients to the same ParseServer. Any suggestions?
The text was updated successfully, but these errors were encountered: