...
The Security → Security Groups page can be reached by clicking the menu item.
| Info | ||
|---|---|---|
| ||
Active Directory Authentication types Flowster Studio uses two values for the authentication type in the Active Directory entries: Secure and Secure Socket Layer. The Secure one: requests secure authentication. When this flag is set, the WinNT provider uses NTLM to authenticate the client. Active Directory Domain Services uses Kerberos, and possibly NTLM, to authenticate the client. When the user name and password are a null reference (Nothing in Visual Basic), ADSI binds to the object using the security context of the calling thread, which is either the security context of the user account under which the application is running or of the client user account that the calling thread is impersonating. The Secure Socket Layer one: Attaches a cryptographic signature to the message that both identifies the sender and ensures that the message has not been modified in transit. Active Directory Domain Services requires the Certificate Server be installed to support Secure Sockets Layer (SSL) encryption. Active Directory supports both Kerberos and NTLM. Windows will first try Kerberos and if all the requirements are not met, it will fallback to NTLM. Kerberos is the default authentication method for AD but it can fallback to NTLM in some cases, but that is handled by Windows itself. Kerberos is used every time a login to an AD is made. As an example, accessing file share by name like \server1\share would invoke Kerberos and should succeed given proper permission. But accessing same file share using IP address would invoke Kerberos first and fail (as there is no SPN for IP Address) and then fail over to NTLM. Here are some links for a better understanding of how the two protocols are working: https://msdn.microsoft.com/en-us/library/bb742516.aspx https://blogs.msdn.microsoft.com/chiranth/2013/09/20/ntlm-want-to-know-how-it-works/ |
User Roles
Flowster Studio defines following user roles and permissions:
...
Users are grouped in Security Groups of the type presented above. The membership and permission of the user is valid only on the parent tenant. If the same user exists in another tenant, the role and permissions will be defined when accessing that tenant via Switch Tenant option in Administrator/Portal/Designer.
Security Groups
...
SuperAdmins
During installation, a super admin user must be entered in order to successfully install the application on a computer. The Super Admin set during installation, can be a custom user or selected from an Active Directory OU, is the only one that can access Flowster Studio components at login. He will be the only one that can define other Active Directory, Google, Azure or Local/Custom users/groups as super admins, administrators or users, by adding them into specific security groups types.
...
All users from this group type can access all Flowster Studio components without the need of creating a Permission Role (e.g. case for administrators groups). Only users from the SuperAdmins group will have visibility and control over this group in the Security Groups page.
...
Admin Group/User Group
Administrator gives users the possibility to create unlimited number of security groups and subgroups , as well as adding Active Directory, Google, Azure or Local users or groups into manually created groups.and adding members from all previously defined authentication providers or custom/local users if no authentication provider is defined.
Admin Group type matches the Admin role described above and similar, User Group type matches the User role.
Add group/subgroup
- Click the Add button to add a new security group. The Add new group window will open.
...
- select a group and move to the properties area.
- select the child that needs to be deleted from the Members grid.
- click the Remove Child button (if the user/group is not member in any other groups, it will be deleted, otherwise it will only be removed from the selected group).
- or select a child and right click on it from the context menu click on the Delete button
Execution Groups Assignment
The super admin can configure which Security Group has access to which Execution Group (For more details regarding execution groups and agents, please visit Execution Groups page). An admin that belongs to a Role that has permission to configure security groups -> execution groups mappings can configure for other security groups only the execution groups that are visible to him.
...