written by Tim.Rice
I’ve been using IEM since it’s early days as BigFix. One of the mantras that was repeated to me was “Do not delete acounts” once created. Disable YES, Delete No. This was because any content or actions created by the account were ‘signed’ by the Console Operator account.
With the move to keep all the signing keys in the database, does this allow us to ‘safely’ delete Console Operator accounts?
written by BrianPGreen
It should be safe to delete console operators. Here’s what happens (and as far as I know, has always happened when deleting operators):
User content in their operator site is deleted. This includes any fixlets in their operator site, and any actions taken by a non-master operator.
All other content is re-signed. So any content created by the user that’s in a custom site, and any actions taken by a master operator stay in place.
Does this answer your question?
written by Tim.Rice
Thanks Brian.
written by jgstew
In our environment we delete inactive users automatically after a year of non-use. The only thing to be concerned of is the loss of custom content in their op site, which could be backed up automatically before deletion.
Hi James,
Is there a automated way to delete operators not loggedon for 60 days? Thanks
This can certainly be automated via the REST API ( https://developer.bigfix.com/rest-api/ ). Aside from deleting the operator, you can also disable their ability to log in as an initial measure prior to deletion after perhaps a longer period of time.
This past week I ran into an issue in which an operator that was removed and then had their back end data removed via the audit trail cleaner tool caused the analyses that the operator had activated to become de-activated. This impacted the SCA application in which the analyses displayed as <not activated>. To workaround the situation, another active operator was able to re-activate the analyses to correct the issue.
I posted a short TechNote regarding the issue.