Edit: Found it, Thanks.
I know nothing about PHP so it might not be a universal error at all…
omnigeek.robmiracle.com/2012/04/15/using-corona-sdk-with-rest-api-services/
On this link I had a lot of trouble with Rob Miracle’s PHP script until I removed
the “md5” next to ($password) about halfway through the code.
… Thought I would document this somewhere on the internet so that maybe it could help someone else. I have no idea how to place this in any context.
Did you read this bullet point:
password — another varchar string, 64 bytes long is sufficient. We are
going to use an MD5 hash process to one-way encrypt the passwords in the
database, we won’t be using MySQL’s “Password” encryption.
The idea is that when you create the username/password combination and store it in the database, instead of using MySQL’s password function to encrypt the password, you make an MD5 hash string instead. This is a one way encryption of the data and can’t be undone.
Then when you receive the password from the REST client and finish base64 decoding it, you convert it to an MD5 hash and then compare the two values.
Were you getting a specific error or was it just not comparing the passwords? I suspect the latter.
Did you read this bullet point:
password — another varchar string, 64 bytes long is sufficient. We are
going to use an MD5 hash process to one-way encrypt the passwords in the
database, we won’t be using MySQL’s “Password” encryption.
The idea is that when you create the username/password combination and store it in the database, instead of using MySQL’s password function to encrypt the password, you make an MD5 hash string instead. This is a one way encryption of the data and can’t be undone.
Then when you receive the password from the REST client and finish base64 decoding it, you convert it to an MD5 hash and then compare the two values.
Were you getting a specific error or was it just not comparing the passwords? I suspect the latter.