> Does "db.person.id.writable = False" only apply to SQLFORMs?
yes. On Tuesday, 8 April 2014 18:31:54 UTC-5, Henry Nguyen wrote: > > Our product is using the @request.restful() decorator to specify REST > endpoints for our resources. During testing, I noticed that I can specify a > PUT request var of "id=x" where x is some new id and the id of that row > will change to x. This is even WITH "db.table.id.writable = False." > > The PUT method is defined as follows: > > def PUT(table_name, record_id, **vars): > return db(db[table_name]._id==record_id).validate_and_update(** > vars) > > So, for example, on a db with "db.person.id.writable = False", a request > to "http://127.0.0.1:8000/appname/default/api/person/1?id=100" will > modify the person row with id 1 to be id 100. > > This seems like a relatively major problem... if a user were to be clever > enough to play around with our UI and figure out the REST calls being made, > he/she could potentially mess with all the ids and relationships of the > resources, at least for that particular account (and any other resources > we've exposed). > > Am I missing something? Does "db.person.id.writable = False" only apply to > SQLFORMs? Is there some other way to prevent modification of the id field? > > Thanks ahead of time for any help. > -- 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.