Content Data Error Logged Parse
Contents |
Support Search GitHub This repository Watch 661 Star 11,381 Fork 2,978 ParsePlatform/parse-server Code Issues 93 Pull requests 16 Projects 0 Wiki Pulse Graphs New issue Queries a required certificate is not within its validity period when verifying against the current system never fail with 'InvalidSessionToken' error when user is logged with legacy session
Capi2 Error 4107
token #1605 Closed DanGTZ opened this Issue Apr 23, 2016 · 7 comments Projects None yet Labels None yet Milestone
A Required Certificate Is Not Within Its Validity Period Windows 10
No milestone Assignees No one assigned 4 participants DanGTZ commented Apr 23, 2016 • edited Check out this issue for an ideal bug report. The closer your issue report is to
What Is Capi2
that one, the more likely we are to be able to help, and the more likely we will be to fix the issue quickly! For implementation related questions or technical support, please refer to the Stack Overflow and Server Fault communities. Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Server! You've met the prerequisites. capi2 4107 You're running the latest version of Parse Server. You've searched through existing issues. Chances are that your issue has been reported or resolved before. Environment Setup Parse hosted app has only legacy user sessions Database migration has been done to MongoDB 3.0.10 running on a AWS instance Local Parse-Server on Node 5.10.1, that point to the migrated databse on AWS iOS client, using SDK 1.12.0, that has a user already logged with the legacy user sessions, and that point to a local Parse-Server Steps to reproduce Launch the iOS client Make it trigger a ParseQuery that don't need any specific permission to succeed => The query returns with no error and the data are OK Make it trigger a ParseQuery that read data and need permission to succeed, like a fetch() on the current user => The query returns code 101 Make it trigger a ParseQuery that modify data and need permission to succeed, like a save() on the current user => The query returns code 206 The problem is that the queries doesn't return the error 209 as explained in the Session Migration Tutorial here : https://parse.com/tutorials/session-migration-tutorial So it'
Support Search GitHub This repository Watch 65 Star 459 Fork 254 ParsePlatform/Parse-SDK-JS Code Issues 42 parse.com javascript tutorial Pull requests 5 Projects 0 Wiki Pulse Graphs New issue I'm a required certificate is not within its validity windows 10 authenticated, but no `x-parse-session-token` header in requests #236 Open yonahforst opened this Issue Mar 21, 2016 a required certificate is not within its validity period windows 7 sp1 · 3 comments Projects None yet Labels None yet Milestone No milestone Assignees No one assigned 2 participants yonahforst commented Mar 21, 2016 I'm using this https://github.com/ParsePlatform/parse-server/issues/1605 SDK in a react-native app. I'm logging into facebook using a separate SDK, then logging into parse using the authdata returned from facebook. I get a success from the login method, along with the correct userID. When I try to make changes to the user I get ParseError { code: 206, message: 'cannot modify https://github.com/ParsePlatform/Parse-SDK-JS/issues/236 user kbMU83TgIi' } looking at the server logs, it seems that I'm not sending the session-token header in my requests. This is even weirder because I'm starting the server with enableAnonymousUsers false, this should prevent me from even reading the user, right? right. But you can see in the server logs below that I'm able to read even without a session-token parse-server --appId APPLICATION_ID --masterKey MASTER_KEY --facebookAppIds [******] --enableAnonymousUsers false Here's my Parse.js helper class import ParseSDK from 'parse/react-native'; class Parse { constructor(props) { ParseSDK.initialize("APPLICATION_ID", "JAVASCRIPT_KEY"); ParseSDK.serverURL = 'http://localhost:1337/parse' } loginWithAuthData(authData) { return ParseSDK.FacebookUtils.logIn(authData) } getPlayer(userID) { return new ParseSDK.Query(ParseSDK.User).get(userID) } updatePlayer(userID, data) { return new ParseSDK.Query(ParseSDK.User).get(userID) .then(player => { for (var key in data) { player.set(key, data[key]); } return player.save() }) .catch(error => { console.log(error) throw error }) } } let parse = new Parse(); module.exports = parse; here are the parse-server logs: GET /parse/classes/_User { host: 'localhost:1337', 'content-type': 'text/plain', connection: 'keep-alive', 'if-none-match': 'W/"f3-bvP3+2p060DRcuxFBao33g"', accept: '*/*', 'accept-lang
File GitHub Using the JavaScript SDK, we can extend the canonical Backbone todo application with user authentication and data persistence across devices. Because our https://parse.com/tutorials/todo-app-with-javascript SDK is based on Backbone, extending this application to use Parse is a https://www.parse.com/questions/unable-to-login-in-javascript-app-while-signup-worked-once-error-100-every-time breeze. This tutorial will guide you through the code for the todo application. You can play around with the live application here. You'll note that the entire application is composed of simple static files. This is the beauty of letting Parse handle the backend for your JavaScript app. Dependencies a required The app requires: Underscore jQuery Note that it does not require Backbone since the Parse JavaScript SDK is a fork of Backbone and does not require any other JavaScript library. Here, we're using jQuery and Underscore for elements that are specific to this app, but you can choose to use any library you want. Templates We use Underscore templates for all a required certificate the views. They are directly placed in index.html as script blocks. For example, this is the template for a single todo item: User Authentication We've extended the typical todo app with user authentication, which allows you to login and manage your todo items from multiple devices. Fortunately, adding this functionality is a breeze with Parse. First, we create a main view called AppView which will manage 2 subviews: the LoginView and ManageTodosView. Basically, we've now added a login screen in front of the usual todo app. We simply test to see if there is a logged in user to determine which view to show: if (Parse.User.current()) { new ManageTodosView(); } else { new LogInView(); } The login view shows two forms, one to login and one to sign up for a new account: