Becomes problematic with Web Services.

J.Ja

And Timers. And Proceses.

J.Ja

Hi Justin James

Could you please explain as how the roles properties could be problemetic with web services, timers and processes.

Because you don't have a user and role when the action is being called via timer or process. 

Yup, exactly. All three scenarios, the system is running as an anonymous user, so you need to perform a login, and there's no clean way to do that in a way that both works AND is secure. Even then, once you define a service account for these systems, and grant them enough roles... it suddenly looks like you need to have an anonymous, unnamed user with super admin right... :(

J.Ja

I think we can't bind database operations with roles. as a developer while DB operation always needs more attention then accessibility.