I don't think there is any problem with that... Though make sure this fake user can't log, set it registration_key to "blocked", so no one will be able to brokein your system with the fake user that you forgot change password or have a weak password...
I would suggest you to alter the auth model with custom auth and make the user_id field of auth_membership not mandatory, though it's a bad idea since it may weaked the RBAC of web2py... Richard On Tue, Jun 16, 2015 at 12:06 PM, Alex Glaros <alexgla...@gmail.com> wrote: > In addition to people having roles in auth_membership, I give objects > roles too with extra field: superObjectID. For example an address can have > many roles. > > But user_id field is mandatory and objects don't have user_id. > > Is there a problem with populating auth_membership.user_id with the same > manufactured person id for all object-based records just to be able to add > records? > > thanks > > Alex Glaros > > -- > 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 web2py+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
