I am new to Parse.com and am trying to test the data I have created on their platform but it is not going through. I have followed the book am reading and it's time to test the data I have created on Parse but it's not working.
I am supposed to type the following address into the browser and receive all the data I have created under the "Products" class as JSON in the browser. I am doing it to test it if it is working.
https://<appID>:javascript-keys=<jsKEY>#api.parse.com/1/classes/Products
appID is replaced with my Parse-applicationID and jsKEY is replaced with my Parse-JavascriptKEY. When I enter the above address into the browser, a dialog box appears asking me to enter my username and password. I typed my www.Parse.com username and password but its not working.
First, I receive a confirmation box with the following message:
You are about to log in to the site "api.parse.com" with the username "<appID>".
appID is the application ID from parse.com
I will click OK and then I receive a prompt dialog box with two input fields for username and password. I enter my parse.com username and password but then it does not work. I also try to use the <appID> as the username and with the parse.com password but still it does not work.
The dialog box means that the authentication failed, so they ask for your username and your password again. The URL scheme is https://user:password#api.parse.com/1/classes/Products. So when the dialog ask for your username and password it actually ask for your appID as username, and your jsKey (with the string "javascript-key=" in front of it) as password.
The issue here is that you are adding a s at the end of key in the string javascript-key=.
Related
I've added 3 UITextFields to create a new account by entering a username in email address format, a new password and a password confirmation. As suggested in Enabling Password AutoFill on a Text Input View. I have configured the username field like this
userTextField.textContentType = .username
userTextField.keyboardType = .emailAddress
and the new password fields like this
newPasswordTextField.textContentType = .newPassword
confirmPasswordTextField.textContentType = .newPassword
Now, when the users enters an email address as username the newPasswordTextField is pre-filled with a suggestion for a strong password (as expected), but the confirmPasswordTextField isn't filled with the same suggested password.
When the user directly taps into the newPasswordTextField without entering a username before both newPasswordTextField and confirmPasswordTextField are pre-filled with the same suggested password (also as suggested).
How can i combine this both situations that after the user enters a username both password fields will be pre-filled with the same password?
I was able to do autocomplete for 2 password fields by declaring the contentType of the first field as: .password
.username
.password
.newPassword
iOS 14 update
The answer from cornr worked for iOS 12 and 13.
However, it fails since iOS 14 in our app, as it will now request access to Keychain to auto-fill the stored password.
It seems that per iOS 14 Apple made it finally match their docu example to create a new account or changing the password. This means that for both password fields .newPassword should be used.
Having that said, suggesting a strong password fails entirely for us on iOS 14.2. For more details see this post.
When a user initially signs up through my app on Parse.com, they supply a username, an email address, and a password.
They verify that email address before they can start using the Parse.com functionalities. So now the user has a valid username, email address and password.
Then, consider this scenario:
1) The user changes his or her email address. 2) The user fails to validate the new email address. 3) The user doesn't use the app for a while. 4) The user forgets his or her password. 5) The user asks to reset the password.
If the user used his or her old email address for the password reset, that address is now gone and the user won't be able to reset the password using that email address.
If the user used the new email address, that address is not verified. Furthermore, it might not have been verified because it could have been typed in wrongly. So the user won't be able to reset the password using that email address.
How is this supposed to have gone down? Is there any way to keep the old email address until the new email address has been verified? That is the only way I can see that this would work.
Have you tried to use the Trigger features from Parse CloudCode?
https://parse.com/docs/cloudcode/guide#cloud-code-aftersave-triggers
Here you can perform code before or after some Object changing. So you can do what you suggested in the bottom of your question: save in another field de old email when the email or emailVerified fields changes.
i forgot my username & password but when i was trying to reset my password or username following message was display: Notice
Reset password failed: Invalid email address
Log into your database via phpMyAdmin
enter the users table in the left menu.
Find the user you want to reset the password for and click the edit icon next to them.
Next to "password", choose MD5 in the drop down, type in a new password, and then click Go.
I am unable to create an account at Heroku.com for some reason. Note that I do not have an account and am trying to create one.
I am able to click "Sign Up" on the home page, input my email address, receive the validation email, follow the link from validation email to page where input password and then am supposed to click "Save". At this screen, my email address has already been filled out (since I followed the link from the email) so I just pick a password, and put the same password in the "Confirm Password" box.
At this point I would expect the "Save" button to light up (or allow me to click it) but nothing happens when I click it.
I would check the Heroku site for help but am required to log in before getting help.
Using Chrome on Win 7. Using Lastpass for password management.
Heroku requires that the password be typed in rather than automatically added with something like Lastpass. Once the password has been typed in, the "Save" button will light up and allow you to proceed.
I need to implement facebook-connect to a website where users already might have their internal accounts. If internal account doesn't exist, it should be created from facebook credentials. Also it should be possible to link an existing account to facebook account. The technical implementation is clear to me, but I am more interested about a practical, optimal, and understandable user activity workflow.
1) My initial idea was to have a login form with user and password fields and two buttons: "connect with facebook" and "login". If "login" is pressed, the internal account is normally logged in. If "connect with facebook" is pressed, the user is connected to facebook and then depending on the state of user and password, I could retrieve the internal user and bind it with facebook user, or create a new internal user and bind it to facebook user, or retrieve the internal user that is binded to the facebook user. However, there I see some gotchas in the workflow. What if the user and password entered are of a different internal user than the one that is binded to the facebook account?
I will try to illustrate the problem in pseudocode:
if "login" is pressed:
internal_user = authenticate(username, password)
if "connect to facebook" is pressed:
facebook_user = get_facebook_user()
if username and password are filled in:
internal_user = authenticate(username, password)
if facebook_user has no internal_user:
facebook_user.bind_internal_user(internal_user)
else:
# conflict! what to do with it?
# facebook_user.get_internal_user() != internal_user
else:
if facebook_user has internal_user:
internal_user = facebook_user.get_internal_user()
else:
internal_user = facebook_user.create_internal_user()
internal_user.login()
Also users might get confused asking themselves if they need to enter facebook username and password or the username and password of the website.
2) Another option could be to have a login form, connect to facebook, and registration form as three different options, where connect to facebook would either get or create an internal account; and then a separate optional form for logged-in users to bind their facebook accounts. But then again there would be possibilites left to create a duplicate internal account.
What are the best practices to deal with that? What are the other websites using mostly?
Login form:
[username] |
[password] | or [fbconnect button] with facebook
[ok] |
(two mutually exclusive sections "either or", you don't need to fill out the login form if you use facebook)
Once a user is connected with FB and you don't have associated user account for this uid then you popup another form:
Welcome,
Please choose username for this site:
[username] [ok]
(you can prompt to select a password as well if you want)
----------------------------------------------------
If you already have an account on our site please enter your credentials:
[username]
[password]
[ok]
After this step you should be covered - no matter which way they chose the result should be the same.
Usually you don't prompt for password for facebook connected users during login, they just use facebook connect button, so randomly generated password would do. If you want to create full scale account that could be used without facebook then you prompt for a password (but still don't use it for facebook login).
FBConnect should ignore your username/pass, in your database you need to store the fb tokens which will be returned from a fb connect login. If the user successfully logs in you will be redirected to a page of your choosing where you can take that fb token and compare it to the database and ignore the username/password. The username/password they filled in on the form will be ignored when fb pops up its own login window.
I hope that answers your question.