I have a situation where some of the code needs to re-schedule the specific timer job and start it according to new schedule. The timer jobs actually writes (need permissions) into the SharePoint configuration database.
I know it's a bit tricky situation because the code needs to be executed and must have the Farm administrator permission for manipulation of SharePoint configuration Database. We also know that our majority of code runs under the application pool account and of course we don't wanna promote our application pool account as a Farm Administrator account (as per Best practices).
What are the alternative scenarios we have at the moment?