Chat now with support
Chat with Support

Identity Manager 8.1.5 - Administration Guide for Connecting to G Suite

Mapping G Suite in One Identity Manager Synchronizing G Suite Managing G Suite user accounts and employees Provision of login information for G Suite user accounts Managing G Suite entitlement assignments Mapping of G Suite objects in One Identity Manager
G Suite customers G Suite user accounts G Suite groups G Suite products and SKUs G Suite organizations G Suite domains G Suite domain aliases G Suite admin roles G Suite admin privileges G Suite admin role assignments Reports about G Suite objects
Handling of G Suite objects in the Web Portal Basic data for managing G Suite Troubleshooting the connection to a G Suite environment Configuration parameters for managing G Suite Default project templates for G Suite API scopes for the service account Processing G Suite system objects Special features in the assignment of G Suite groups About us

Administrative user accounts

An administrative user account must be used for certain administrative tasks. Administrative user accounts are usually predefined by the target system and have fixed names and login names, such as Administrator.

Administrative user accounts are imported into One Identity Manager during synchronization.

NOTE: Some administrative user accounts can be automatically identified as privileged user accounts. To do this, in the Designer, enable the Mark selected user accounts as privileged schedule.

Related topics

Providing administrative user accounts for one employee

Prerequisites

  • The user account must be labeled as a personalized admin identity.

  • The employee who will be using the user account must be labeled as a personalized admin identity.

  • The employee who will be using the user account must be linked to a main identity.

To prepare an administrative user account for a person

  1. Label the user account as a personalized admin identity.

    1. In the Manager, select the G Suite | User accounts category.

    2. Select the user account in the result list.

    3. Select the Change master data task.

    4. On the General tab, in the Identity selection list, select Personalized administrator identity.

  2. Link the user account to the employee who will be using this administrative user account.

    1. In the Manager, select the G Suite | User accounts category.

    2. Select the user account in the result list.

    3. Select the Change master data task.

    4. On the General tab, in the Person selection list, select the employee who will be using this administrative user account.

      TIP: If you are the target system manager, you can choose to create a new person.

Related topics

Providing administrative user accounts for several employees

Prerequisite

  • The user account must be labeled as a shared identity.

  • A dummy employee must exist. The dummy employee must be labeled as a shared identity and must have a manager.

  • The employees who are permitted to use the user account must be labeled as a primary identity.

To prepare an administrative user account for multiple employees

  1. Label the user account as a shared identity.

    1. In the Manager, select the G Suite | User accounts category.

    2. Select the user account in the result list.

    3. Select the Change master data task.

    4. On the General tab, in the Identity menu, select Shared identity.

  2. Link the user account to a dummy employee.

    1. In the Manager, select the G Suite | User accounts category.

    2. Select the user account in the result list.

    3. Select the Change master data task.

    4. On the General tab, select the dummy employee from the Employee menu.

      TIP: If you are the target system manager, you can choose to create a new dummy employee.

  3. Assign the employees who will use this administrative user account to the user account.

    1. In the Manager, select the G Suite | User accounts category.

    2. Select the user account in the result list.

    3. Select the Assign employees authorized to use task.

    4. In the Add assignments pane, add employees.

      TIP: In the Remove assignments pane, you can remove assigned employees.

      To remove an assignment

      • Select the employee and double-click .
Related topics

Privileged user accounts

Privileged user accounts are used to provide employees with additional privileges. This includes administrative user accounts or service accounts, for example. The user accounts are labeled with the Privileged user account property (IsPrivilegedAccount column).

NOTE: The criteria according to which user accounts are automatically identified as privileged are defined as extensions to the view definition (ViewAddOn) in the TSBVAccountIsPrivDetectRule table (which is a table of the Union type). The evaluation is done in the TSB_SetIsPrivilegedAccount script.

To create privileged users through account definitions

  1. Create an account definition. Create a new manage level for privileged user accounts and assign this manage level to the account definition.
  2. If you want to prevent the properties for privileged user accounts from being overwritten, set the IT operating data overwrites property for the manage level to Only initially. In this case, the properties are populated just once when the user accounts are created.
  3. Specify the effect of temporarily or permanently disabling or deleting, or the security risk of an employee on its user accounts and group memberships for each manage level.
  4. Create a formatting rule for the IT operating data.

    You use the mapping rule to define which rules are used to map the IT operating data for the user accounts, and which default values are used if no IT operating data can be determined through a person's primary roles.

    Which IT operating data is required depends on the target system. The following settings are recommended for privileged user accounts:

    • In the mapping rule for the IsPrivilegedAccount column, use the default value 1 and set the Always use default value option.
    • You can also specify a mapping rule for the IdentityType column. The column owns different permitted values that represent user accounts.
    • To prevent privileged user accounts from inheriting the entitlements of the default user, define a mapping rule for the IsGroupAccount column with a default value of 0 and set the Always use default value option.
  5. Enter the effective IT operating data for the target system.

    Specify in the departments, cost centers, locations, or business roles which IT operating data should apply when you set up a user account.

  6. Assign the account definition directly to employees who work with privileged user accounts.

    When the account definition is assigned to an employee, a new user account is created through the inheritance mechanism and subsequent processing.

TIP: If customization requires that the primary email addresses of privileged user accounts follow a defined naming convention, create the template according to which the primary email addresses are formed.

Related topics
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating