This section covers changes between release on the following topics:
- Authorization to the platform
- User roles
- Permissions of roles
- Authentication methods
- User management
New user management page
The Workspace Users page now centralizes user management tasks in a single dedicated interface.
Except for some uses, the Users area of the Admin Settings page is no longer needed. It has been disabled by default. See below for details.
For more information on the new page, see Workspace Users Page.
You can also explore details of individual users in another new page. See Workspace User Details Page.
Users section of Admin Settings page is disabled
Except for the following situations, all user management functions of the Admin Settings page have been migrated to the Workspace Users page. The Users section should be re-enabled for the following situations:
- Configure user principal values for integration with:
- Enterprise SSO
- A Hadoop cluster
- Kerberos security
Configure user accounts for the Trifacta admin role
NOTE: The Trifacta admin role is a super-user role across the entire platform. It should be assigned to a small number of accounts.
For more information on re-enabling the Users section of the Admin Settings page, see Manage Users.
Beginning in Release 7.5, workspace administrators can create and assign roles to workspace users. Each role contains zero or more privileges.
A role is a set of privileges that you can assign to workspace users. Workspace users may have one or more roles.
NOTE: Each current user or newly created user is automatically assigned the
defaultrole, which grants a set of privileges for all governed object types in the workspace.
- A privilege is a level of access to a type of user-defined workspace object, such as flows.
Roles are created and assigned through the Roles page in the Admin console. For more information, see Workspace Roles Page.
Workspace owner role is removed
As of Release 7.5, the workspace owner role has been removed from user access.
The privileges of this role have been collapsed into the
admin role for workspaces, which has full capability to administer the workspace.
Workspace roles govern access to workspace objects.
Platform roles govern access to platform capabilities.
For more information on these distinctions, see Overview of Authorization.
Release 7.1 introduces role-based access controls (RBAC), in which access to Trifacta resources are managed at finer-grained levels. This release introduces the basic RBAC framework and the following key changes.
NOTE: Over the next few releases, additional capabilities will be added to the basic RBAC framework, enabling administrators to provide better and more closely defined access to objects. Check back to this section with each upgrade.
Workspace admin is a super user
Beginning in Release 7.1, the workspace admin is a super-user of the product.
NOTE: In this release, the workspace admin user has owner access to user-created objects, such as flows and connections, within the workspace.
A workspace is a set of users and their objects, such as flows and connections. For more information, see Workspace Admin Permissions.
All upgraded Trifacta admins are now workspace admins
NOTE: If you are upgrading Designer Cloud powered by Trifacta Enterprise Edition, any Trifacta admin users are now workspace admin users. A single workspace is supported in your instance of Designer Cloud powered by Trifacta Enterprise Edition. Additional workspaces are not supported.
NOTE: Any user who is granted the admin role is also granted the workspace admin role, which enables owner-level access to user-created objects in the workspace.
Admin can edit any global connection
After an administrator has made a connection global (available to all users):
- Any administrator can edit the connection.
- All users can use the connection (existing functionality)
- The connection cannot be made private again (existing functionality). Connection must be deleted and recreated.
Menu items unavailable due to account roles
Beginning in this release, menu items may not be displayed to specific users because of their current role assignments.
NOTE: This behavior had existed in previous releases. In this release and future releases, workspace admins may receive inquiries about menu option availability. A user's assigned roles could be a likely source for why a menu option is not available to the user.
Logs from the authorization service may provide insight into access problems. These logs are available for download through the support bundle. For more information, see Support Bundle Contents.
Authorization changes to APIs
Some API endpoints now include information that is specific to the changes in this release for authorization. See Changes to the APIs.
This page has no comments.