×

Supercharge your Proficy solution! Download a free trial of Proficy Operations Hub, CSense analytics, and more. Explore our Proficy 2024 releases!

Home
Security
Domain-Based Security
Windows Domain-Based Security
You can use Windows domain user accounts to manage access to and within Workflow. You can also configure domain user accounts for automatic login on either a global basis or for individual computers.
Configuring Domain-Based Access Control to Workflow Functionality
You can use active directory universal or global groups to control access to Workflow functionality.
Convert between Windows domain and Workflow users
Beginning with Workflow version 2.2, you can convert Workflow users to domain users, and vice versa, by either adding the applicable domain designation to the user's name or removing the designation from the name, respectively.

Workflow IPI
Get Started
Tutorials
Orientation
Configure Your Environment
Security
- Security Overview
- Users and Groups
- Domain-Based Security
  - Windows Domain-Based Security
    You can use Windows domain user accounts to manage access to and within Workflow. You can also configure domain user accounts for automatic login on either a global basis or for individual computers.
    - Windows Domain Users Logging into Workflow
      If you are using Windows user names and passwords within Workflow security, be aware that Windows user accounts must have the policy Access this computer from the network applied under the local security policy. By default, this policy is assigned to the groups Users and Everyone on the local machine.
    - Authenticate Windows Domain Users for Vision Calls
      Vision uses a token to make a secure call. For Windows authentication, the Proficy STS service needs to query the domain controller to retrieve groups that the user belongs to. This group information is used to validate the Windows user.
    - Password Expiration Considerations
      When Workflow security is synchronized with Windows security, passwords can expire.
    - Configuring Domain-Based Access Control to Workflow Functionality
      You can use active directory universal or global groups to control access to Workflow functionality.
      - Assigning operating system rights to Windows domain user accounts
        When you use Windows security in Workflow, user accounts that need to log in to a machine must have the Act as Part of the Operating System right enabled in the local security policy.
      - Set Windows passwords to expire
        One of the benefits of using Workflow with Windows security is that you can set Windows passwords to expire.
      - Limit the number of invalid login attempts
        When a Workflow user is connected to a Windows domain user account, you can set an account lockout threshold, which prevents a user from accessing the account after he enters the incorrect user name or password beyond the number of acceptable times. When the account lockout threshold has been reached, the account is disabled.
      - Associate Active Directory universal or global groups with Workflow groups
        Domain users are Windows users who are members of one or more Windows domain groups.
      - Automatically create Workflow user accounts for Windows domain user accounts
        You can automatically create a Workflow user when a Windows domain user logs into Workflow client for the first time.
      - Manually add a Windows domain user to Workflow
        You can use Windows domain user accounts to manage access to and within Workflow.
      - Convert between Windows domain and Workflow users
        Beginning with Workflow version 2.2, you can convert Workflow users to domain users, and vice versa, by either adding the applicable domain designation to the user's name or removing the designation from the name, respectively.
      - Active Directory Groups and Domain Users
        The Domain Users tab displays the list of active directory universal or global groups and Windows domain users who are members of those groups. You can map additional active directory groups to the current Workflow group or remove mapped active directory groups.
    - Key Sets
      Key sets are groups of permissions, based on areas of operation within your facility, that define the operations a group of users can perform.
    - Login and Logout Capabilities
      Workflow access can be configured in multiple ways. You can configure automatic login and logout on individual computers, on all computers in your system, or on a subset of computers in your system. You can also retain manual login and logout on a global basis or on specific computers.
    - Workflow User Password Security
      Administrator users have the ability to make changes to the security settings in Workflow, including configuring lockout thresholds, re-enabling locked out user accounts, configuring password complexity, and determining whether or not users can change their passwords.
Resource Information and Configuration
Data Administration
Forms and User Displays
Building and Configuring Workflows
eSOP
ActiveX Task Controls
Service Interfaces
Operator Task List in the Workflow Client
Best Practices

Convert between Windows domain and Workflow users

Beginning with Workflow version 2.2, you can convert Workflow users to domain users, and vice versa, by either adding the applicable domain designation to the user's name or removing the designation from the name, respectively.

Prerequisites: Manually add a Windows domain user to Workflow; Add Users and Personnel Classes

Procedure

In the navigator, click Personnel > People.
In the Folders list, click the user that you want to convert the type for.
In the Displays panel, select Production Management > S95 Model Editor.
On the Details tab, click the Edit link.
Edit the Name value as appropriate to the conversion direction:
- If you are converting a Workflow user to a Windows domain user, edit the value to reflect the format <Fully Qualified Windows Domain Name>\<Windows Account Name> (for example MyDomain.MyCompany.com\RobertGray).
- If you are converting a Wlindows domain user to a Workflow user, remove the domain designation and backslash from the value.
Click Save.

What to do next

If you convert a Windows domain user to a Workflow user, you must subsequently specify access credentials for the user, and, if the permissions that were previously afforded the user, which carry over with the conversion, are no longer appropriate, adjust group associations.