<style> .text-span-6 { background-image: linear-gradient(99deg, rgba(170, 163, 239, .5), rgba(125, 203, 207, .5)); border-radius: 50px; padding-left: 15px; padding-right: 15px; } #title-text { display: none; } .panelgradient { background-image: linear-gradient(180deg, #d5def0, whitesmoke); border-radius: 8px; flex-direction: column; justify-content: center; align-items: center; padding: 4rem; display: flex; position: relative; } </style> <div class ="panelgradient"> <h1 style="text-align: center;">Security <br> (Users and Roles)</h1> </div> |
Here You Can:
On this page:
The Security Module secures the data exchange between the platform and external databases.
UsersAnyone accessing the project, either in engineering or runtime mode. |
PermissionsPermissions are set levels of access for each user that determine what they can/ cannot do within the software. |
PoliciesPolicies manage requirements on User Identification and Session control. |
RuntimeUsersThese users are created and retrieved from an external encrypted SQL database or other identification servers. |
Managing user roles in FactoryStudio involves assigning a role to each user that defines their level of access to various components of the project. Each role has its permissions, which can be customized to meet the security requirements of your organization.
External Users in this context refers to users who are not part of the organization but need access to specific components of the project. This can include contractors, clients, or third-party vendors. These users are typically managed via RuntimeUsers or integration with Active Directory and LDAP.
FactoryStudio provides several tools to secure project settings. By assigning Permissions and Policies, administrators can control which users have access to specific project settings and features. This ensures that only authorized users can make changes to critical project settings.
Securing runtime involves managing user sessions in client displays by setting password requirements, session restrictions, and e-signature settings. FactoryStudio also allows administrators to monitor client connections and manage active sessions.
Users, Permissions and Policies
For a summarry of the Security Configuration, go to Security Module Overview
That page presents the basic configuration steps and properties for Users, Permission and Policies.
The next section, presents the configuration of those elements in further details.
Each user is assigned to a Security Group defined in Permissions and a Session Policy configured in the Policies.
Security module configuration workflow | |
---|---|
Action | Where |
Edit Users | Security → Users |
Define security Permissions | Security → Permissions |
Define security Policies | Security → Policies |
Manage RuntimeUsers | Security → RuntimeUsers |
Runtime Users are either defined in an external database or created dynamically using the CreateUser method. They can log in and use remote operation displays similarly to users specified in the Project configuration.
→ Read more about RuntimeUsers properties.
The platform can automatically execute user credentials validation and user connection identification using native Windows Active Directory integration, available for users connecting from Windows operating systems.
→ Read more about Windows AD / LDAP Server.
When Windows AD integration is unavailable, automated identification can still be achieved using a business server-defined LDAP server.
→ Read more about Windows AD / LDAP Server.
→ Read more about Security Runtime Execution.
Track and manage active connections, enabling efficient troubleshooting and resource allocation.
? Read more about Monitoring Client Connections.
Modify the login page, fine-tune user validation, and incorporate custom logic into the client startup process for a tailored login experience.
? Read more about Customizing Login Procedures.
Regulate user access and interactions within displays and scripts to promote a secure and efficient work environment.
→ Read more about Managing Users on Displays and Scripts.
The Security namespace contains all runtime information regarding the security system. The Client
object has information about the current user logged at that client station.
Examples | |
---|---|
Client.Username | The property is the name of current logged user. |
Client.CurrentUser | Reference to a data structure with all the information of the currently logged-in user. |
→ Read more about Objects and Namespaces.
Troubleshooting and Common Issues:
Best Practices and Recommendations:
In this section: