One typical day at work, we see some user roles being added and deleted in the instance. We had raised a Hi ticket to understand what scripts could possiblt be doing this. This is the response we got:
This is happening due to a sys_execution_tracker running daily as a job, which is introduced as part of the Paris release. Here is the excerpt from the Product documentation on this.
For custom roles, licensing performs an entitlement check to determine the access and permissions of your custom roles and tables. For this process, a temporary user with the name licensing.role.testingappears on your instance. The system grants this temporary user one role at a time to determine the roles that can perform licensable actions such as fulfillment of requester actions. Based on the licensing check, the system allocates the roles by the preceding logic.
The subscription summary job happens automatically each night or when you select the Update allocation totals button. The licensing.role.testing user does not count towards allocation totals and is removed after the process completes. The job is processed on your local instance only to calculate data used by Subscription Management.Here is the product doc for the same.
As part of the automatic allocation mentioned above, the system does indeed create a test user and assigns different roles to auto-determine the access allowed per role. Thus, you are seeing evidence of this in the log files. We had reached out to Development on this and they mentioned they are also working on a fix to turn off all workflows when we add/remove roles from his test user to remove some of the noise in the logs.
Comments