Skip to content

Bug in all Parse releases above 2.2.23: ClientKey cannot be empty #3936

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

Closed
halavins opened this issue Jun 16, 2017 · 2 comments
Closed

Bug in all Parse releases above 2.2.23: ClientKey cannot be empty #3936

halavins opened this issue Jun 16, 2017 · 2 comments

Comments

@halavins
Copy link

halavins commented Jun 16, 2017

Dear Sirs,

I've updated my Parse Server and found out that the latest Parse Server versions, including 2.4.2 do not allow me to connect to it if I use "PARSE_SERVER_CLIENT_KEY": "". The problem is that all our released apps use the blank key to connect to Parse Server, so we can't change it to any other value.

I see there was a "bug fix" on Feb 9, it says that Parse allows empty / null client key, but it's not true:
#3497

We tried downgrading the Parse Server to 2.2.23. It works. If we upgrade it to 2.2.24+, we can't connect to the server anymore with ClientKey = "". If we change the ClientKey to anything but "", it works. Nevertheless, we cannot change the client key to anything but "", because most of our clients have already downloaded the apps with ClientKey = "".

  • Server

    • parse-server version 2.2.24 - 2.4.2
    • Operating System: Ubuntu
    • Hardware: 8 CPU, 8 GB RAM, 150GB Disk Space
    • Localhost or remote server? Rackspace
  • Database

    • MongoDB version: 3.2.8
    • Storage engine: WiredTiger
    • Hardware: 250GB
    • Localhost or remote server? ObjectRocket

LOGS of the XCode, when trying to connect to Parse Server 2.4.2 with ClientKey = "" (the same key is in the parse server config ecosystem.json):
{ error : unauthorized }.

@dplewis
Copy link
Member

dplewis commented Jun 16, 2017

Look at what I wrote here. Its not your clientKey its probably your other keys.

Try changing your javascriptKey: 'unused'

#356

@stale
Copy link

stale bot commented Sep 18, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Sep 18, 2018
@stale stale bot closed this as completed Sep 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants