Agents fail when 'Author' user ID is disabled (author retired from company)

JustTheFacts

We have been using OBIEE since it was nQuire and I am amazed we never encountered this problem before. Our company recently downsized and among the unlucky ones were two of our administrator/developers who created a bunch of Agents. Key, critical agents that our field personnel rely on every day. Key, critical Agents which all failed the day that those people's IDs were disabled in our LDAP system.

So Bob123 worked for us for a few years and created many dozens of agents. All of these agents are set to "Run As" a generic user, since we don't have any row-level data security concerns. All of the agents show Bob123 as the Author on their properties page, and Bob123 is the "User ID" value in the S_NQ_JOB scheduler table.

Bob123 got let go and his LDAP entry got deleted yesterday. Today all of his agents failed with invalid user ID/password. We think we have a workaround, which is to hack our generic (admin-level) user ID into S_NQ_JOB and then also hack the .atr files to replace Bob123 with the generic ID. We have tested this

My question is this: is there a workaround or a best practice for creating Agents in an LDAP/SSO environment? It occurs to me that any organization would run into this pretty serious issue as people come and go. You hire a guy to build out a bunch of agents for you, then he leaves and you retire his ID and boom all of "his" Agents stop working.

The only way we can see to prevent this in the future is to use the Act As feature to impersonate our generic user ID whenever we create or edit an Agent. Is that how everybody has to do it, to insulate themselves from failures caused by staff turnover?