cancel
Showing results for 
Search instead for 
Did you mean: 

SAC Security User Best Practice

Sorro
Explorer
0 Kudos

Hello everyone,

I was wondering if there exists a best practice regarding the creation of the basic configuration of the system starting a project, like basic roles, and connections.

We used a consultant user to create all these configurations, but in one point this user was no longer in the project and the customer decided to retire the user from SAC and their Active Directory, and this broke the system access enterely, because some configurations were tied to that user. In the end we had to disable SSO and re create the deleted user in order to re-gain access to the system and then change the ownership of security and connections to another user. It worked.

So the question is if there's a best practice for this? It came to my mind the idea to create a generic system user like "SAC_ADMIN" (which will remain created forever), and with that user create all the content related to security and connections, and only have a pro licence on him when needed, but maybe we're missing something.

Thanks!

Accepted Solutions (0)

Answers (0)