parse.com - Parse iOS Destroy Button (Password Validation Dependent) Client side -

i'm starting create lot more features users in app. i've run app structure issues.

lets have user fooman

fooman wants edit account, delete objects(wall posts), update friends list etc.

fooman logged in of these. footman isn't 1 using device @ moment. it's fooman son (foobaby). foobaby decides son , delete things erroneously. have option users delete account client side. present them alert view confirm that's choice meant select. after confirm that, view populates 'destroy' (or delete button) delete user, plus relations/pointers/data connected it. before button enabled password validation check required it's not done foobaby. however, parse, has proved problematic client side. don't use cloud functions because, well, put, @ point in time app 1 platform , doesn't need use it.

is there workaround has come that's quick/efficient, api friendly validating textfield.text [pfuser currentuser].password whilst maintaining security of course.

i code in objective-c :)

note: have tried numerous things nothing seems work outside of trying log them in against user input (uitextfield), doesn't feel right way in opinion.

i think it's unusual requirement. idea of logged-in user app trusts user. persisted logged-in user on device means app trusts whomever holding device. foobaby trusted, because foodad let him hold phone.

some apps put barrier establish thoughtfulness, parse data browser requiring type name of class before drop it. establishes thoughtfulness, not trust. (for child, guess establishes minimal competence, in case foobaby knows how press buttons, not how spell).

otherwise, can't think of how besides requiring login, mentioned find unappealing (though didn't why). excluding that, don't think there's way without spoiling security keeping in-the-clear copy of password.