Key Concepts and Terms

The Security module's purpose is to ensure secure data exchange between the platform and external databases. The concepts of Users, Permissions, Policies, and Runtime Users ease the Security module's understanding.

Understanding the Security Module

User roles management

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 Definitions

External Users in FactoryStudio 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.

Securing Project Settings

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

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.

Configuring the Security Module

Configuration Workflow

Each user is assigned to a security group defined in Permissions and a session policy configured in the Policies.

Permissions define the level of access users have for project configuration and client displays.

Policies, on the other hand, focus on managing user sessions in client displays, either WPF or HTML5, by setting password requirements, session restrictions, and e-signature settings.

RuntimeUsers

RuntimeUsers are a separate group of users who are either defined in an external database or created dynamically using the CreateUser method, and they can log in and similarly utilize remote operation displays to the users specified in the Project configuration. See RuntimeUsers properties to explore the properties in detail.

AD/LDAP Integrations

Windows AD Integration

Instead of validating the Users again, the credentials in the Project configuration and the identification of the User connection can be automatically executed using our native Windows Active Directory integration. This functionality in only available for the Users connecting from Windows operating systems. For more information, see Windows AD / LDAP Server.

AD/LDAP Server Integration

When the integration with Windows AD is not available, it is still possible for an automated identification using the business server to define an LDAP server to be used by the project. For more information, Windows AD / LDAP Server.

Working with the Security Module

Runtime Execution

For in-depth security runtime understanding, please explore the Security Runtime Execution.

Monitoring Clients Connections

The Monitoring Client Connections empowers you to track and manage active connections. This functionality enables efficient troubleshooting and resource allocation for your project's needs. Please refer to the Monitoring Client Connections for a comprehensive client connections understanding.

Customizing Login Procedures

The Custom Login Procedures enables you to modify the login page, fine-tune user validation, and incorporate custom logic into the client startup process. This allows for a tailored login experience that suits your project's specific requirements. For a deeper understanding of how to customize login procedures and to examine detailed examples, please consult the Customizing Login Procedures.

Managing Users on Displays and Scripts

The User Management on Displays and Scripts enables you to regulate user access and interactions within displays and scripts, promoting a secure and efficient work environment. To acquire an in-depth understanding of user management on displays and scripts, please consult the Managing Users on Displays and Scripts.

Troubleshooting and Best Practices

Troubleshooting and Common #Issues

The Security module may encounter some issues in its operation. Here are some common issues and their solutions:

1. User cannot log in

   • Solution: Ensure that the user is entering the correct login credentials. Check if the user's account is active and not blocked or flagged as deleted. If the problem persists, contact your system administrator.

2. Permission denied error

   • Solution: Check the user's assigned Permissions. Ensure that they have the necessary access rights to perform the desired action. If necessary, update their Permissions or assign them to a different user group.

Best Practices and #Recommendations

To ensure the smooth operation of the Security module, follow these best practices:

1. Regularly update your user list and their associated permissions. This helps maintain security by ensuring that only authorized individuals have access to your system.

   • Recommendation: Conduct a periodic audit of user accounts and permissions. Make necessary updates and remove inactive users.

2. Enforce strong password policies to enhance security.

   • Recommendation: Require users to use complex passwords that include uppercase and lowercase letters, numbers, and special characters. Additionally, encourage them to change their passwords regularly.

3. Keep your system up-to-date with patches and updates.

   • Recommendation: Regular updates and patches often include security enhancements and fixes. Ensure that your system is up-to-date to take advantage of these improvements.

Security Runtime Attributes

The Security namespace has all the runtime information regarding the security system.

The Client object has information about the current user logged at that client station:

To learn about the basic concepts of namespaces and objects, you can refer to Objects and Namespaces.

In this section: