In my case Facebook, LinkedIn, Google are not trustworhy (quite the
opposite). I need - most importantly - to avoid that database entries of
users can be attributed to users.
The users should be mere abstract nodes with properties for me. It's the
abstract node and its properties I'm interested in.
On the other hand I need to know their adresses for billing them, I need to
convince them, that I myself can't relate their personal information in the
database to them. Maybe this two requirements are conflicting each other.
What do you guys think? Is there a solution for this scenario?
(user "Jonathan") -- [raltes to] -- (user-node of X) --- [contains] ---
{Properties: Age, Eyecolor}
I I
(Biling) (Interest)
/Y
Well, web2py was designed with security in mind, such as using the auth
> machanisms, URL signing, etc. Auth works with several methods, from
> tracking passwords in the database to using trusted servers to confirm you
> (CAS and RBAC with Facebook, LinkedIn, Google), use of Captchas, signed
> URLs, etc.
>
> If you think something is missing, describe what you need and see if
> someone already has an answer for it, or has suggestions to handle it
> easily.
>
> /dps
>
>
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
