Live data from Hacker News

Parse launches JavaScript SDK: Parse for Websites

blog.parse.com

1–10 of 112 posts

Re: Parse launches JavaScript SDK: Parse for Websites

#4

Can anyone explain to me how authentication works with JS-based storage client like this? It scares me to think a user might have the ability to store anything via the web on my dime. I feel like I'm missing something.

I am wondering same thing, can somebody explain this please.

Re: Parse launches JavaScript SDK: Parse for Websites

#8

Can anyone explain to me how authentication works with JS-based storage client like this? It scares me to think a user might have the ability to store anything via the web on my dime. I feel like I'm missing something.

There are two main types of security. Object-level, and app-level. Each object gets access controls that are similar to ACLs in Unix systems. That provides for the sort of security that separates different users' data from each other. On an app-level, you can also control per-class which operations are usable. For more detail, see:

https://parse.com/docs/data#security

You should be able use these in combination to secure your app. If you have more specific questions about how to secure a particular use case, drop us an email at feedback@parse.com and we can help figure something out.

Re: Parse launches JavaScript SDK: Parse for Websites

#10

Can anyone explain to me how authentication works with JS-based storage client like this? It scares me to think a user might have the ability to store anything via the web on my dime. I feel like I'm missing something.

I am wondering same thing, can somebody explain this please.

It's relatively easy to do basic HTTP authentication using Javascript. If you're on SSL, that's reasonably secure. Once you're authenticated the server can issue a nonce that identifies you and gives you authorization (role-based access) to various pages/objects/apps based on that nonce.
Post reply on HN