Skip to main content

User Management

  • User can see total numbers of users from Manage/Security path and if they want to create they can create from there clicking on create user button.
    • Also, they can manage users like edit or delete users.
    • If you create user Guzzle will ask some properties like First Name, Last Name, Username, Email and Role.

Guzzle provides two types of Authentication namely:

  1. Native users: Here the user.

  2. Azure Active Directory SSO. We can add new users and consider single sign on with azure.

Users Maintenance#

By navigating to Manage tab and then to Security β†’ Users. User can see list of users and from their admin can manage user by editing and deleting it.

Interface of Users list and how to manage is below

Create Users#

Below are the steps to create new user

  1. Go to Manage menu from top navigation bar

  2. Navigate Security β†’ Users

  3. Click on the "Create Users" button to create a new user. Click on Edit icon to edit existing user and Delete icon to delete existing users

  4. Provide below details and click "Create" or β€œUpdate” button

PropertyDescription
First NameFirst name of the user
Last NameLast name of the user
UsernameThis is the username that shall be used for login into Guzzle. For Azure SSO this should be AAD user name which generally is the email address (also referred to as user principal name)
PasswordThe password of the user
- only applies for Native users
EmailThis is the email of the native user. For Azure SSO this field is automatically populated from username
- This field is not applicable for external users
Security RoleChoose one or more roles: There are four roles Reader, Operator, Contributor and Admin which is described below
note

It’s not possible to convert the native user to External (also referred as SSO) user. The only way to achieve this by deleting existing native user and re-creating it as external user

Guzzle Roles#

  1. Reader β€” Users with this role can view guzzle jobs (read-only) and monitoring roles. They can not run anything, preview anything or test any connections.

  2. Operator β€” Users with this role can do what reader role can do and additionally they can run the jobs.

  3. Contributor β€” Users with this role can do what operator role can do and additionally they can edit the configs including on git, publish to default and also change physical endpoint, environment and computes.

  4. Admin β€” User with this role can do what contributor can do and also they can manage all items in Admin section and setup git-config.

For more information for guzzle roles visit this excel sheet.

Some features are not applicable any more (atlas and file templates).