지금 지원 담당자와 채팅
지원 담당자와 채팅

Identity Manager 9.2.1 - Administration Guide for Connecting to SharePoint

Managing SharePoint environments Setting up SharePoint farm synchronization Basic data for managing a SharePoint environment SharePoint farms SharePoint web applications SharePoint site collections and sites SharePoint user accounts SharePoint roles and groups
SharePoint groups SharePoint roles and permission levels
Permissions for SharePoint web applications Reports about SharePoint objects Configuration parameters for managing a SharePoint environment Default project template for SharePoint

Supported user account types

Different types of user accounts, such as default user accounts, administrative user accounts, service accounts, or privileged user accounts, can be mapped in One Identity Manager.

The following properties are used for mapping different user account types.

  • Identity type

    The Identity type property (IdentityType column) is used to describe the type of user account.

    Table 19: Identity types of user accounts
    Identity type Description Value of the IdentityType column

    Primary identity

    Identity's default user account.

    Primary

    Organizational identity

    Secondary user account used for different roles in the company, for example for subcontracts with other functional areas.

    Organizational

    Personalized administrator identity

    User account with administrative permissions, used by an identity.

    Admin

    Sponsored identity

    User account used for a specific purpose. For example, for training purposes.

    Sponsored

    Shared identity

    User account with administrative permissions, used by multiple identities.

    Shared

    Service identity

    Service account.

    Service

  • Privileged user account

    Privileged user accounts are used to provide identities 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).

Default user accounts

Normally, each identity obtains a default user account, which has the permissions they require for their regular work. The user accounts are linked to the identity. By default, the link between identity and SharePoint user account is set up through the authentication objects to which the user account is assigned. Alternatively, identities can also be directly linked to the user accounts. Such user accounts can be managed through account definitions. The effect of the link and the scope of the identity’s inherited properties on the user accounts can be configured through an account definition and its manage levels.

To create default user accounts through account definitions

  1. Create an account definition and assign the Unmanaged and Full managed manage levels.

  2. Specify how an identity's temporary deactivation, permanent deactivation, deletion, and security risks affect its user accounts and group memberships at each manage level.

  3. Create a formatting rule for IT operating data.

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

    The type of IT operating data required depends on the target system. The following setting are recommended for default user accounts:

    • In the mapping rules for the IsGroupAccount_SPSGroup and IsGroupAccount_SPSRLAsgn columns, use the default value 1 and set the Always use default value option.

    • In the mapping rule for the IdentityType column, use the default value Primary and enable Always use default value.

  4. Enter the effective IT operating data for the target system. Select the concrete target system under Effects on.

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

  5. Assign the account definition to identities.

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

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.

You can label administrative user accounts as a Personalized administrator identity or as a Shared identity. Proceed as follows to provide the identities who use this user account with the required permissions.

  • Personalized admin identity

    1. Link the user account to a pseudo identity using the UID_Person column.

      Use an identity with the same identity type or create a new identity.

    2. Assign this identity to hierarchical roles.

  • Shared identity

    1. Assign all identities with usage authorization to the user account.

    2. Link the user account to a pseudo identity using the UID_Person column.

      Use an identity with the same identity type or create a new identity.

    3. Assign this pseudo identity to hierarchical roles.

    The pseudo identity provides the user account with its permissions.

Privileged user accounts

Privileged user accounts are used to provide identities 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 how an identity's temporary deactivation, permanent deactivation, deletion, and security risks affect its user accounts and group memberships in the 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 IT operating data for user accounts and which default values are used if no IT operating data can be determined through an identity's primary roles.

    The type of IT operating data 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_SPSGroup and IsGroupAccount_SPSRLAsgn columns 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 identities who work with privileged user accounts.

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

TIP: If customization requires that the login names of privileged user accounts follow a defined naming convention, specify how the login names are formatted in the template.

Entering main data of SharePoint user accounts

Each SharePoint user account represents an object from an authentication system. This object can be a group or a user. The group authentication and user authenticated user accounts are select separately in the navigation system.

To edit the properties of a group authenticated user account

  1. Select the SharePoint > User accounts (group authentication) category.
  2. Select the user account in the result list and run the Change main data task.

    - OR -

    Click in the result list.

  3. Edit the user account's resource data.
  4. Save the changes.

To edit the properties of a user authenticated user account.

  1. Select the SharePoint > User accounts (user authentication) category.
  2. Select the user account in the result list and run the Change main data task.

    - OR -

    Click in the result list.

  3. Edit the user account's resource data.
  4. Save the changes.

To manually assign or create a user authenticated user account for an identity

  1. Select the Identities > Identities category.
  2. Select the identity in the result list and run the Assign SharePoint user accounts task.
  3. Assign a user account.
  4. Save the changes.
Detailed information about this topic

Group authenticated user account main data

Enter the following main data of a group authenticated user account.

Table 20: Group authenticated user account main data
Property Description
Identity

Identity that uses this user account.

  • An identity is already entered if the user account was generated by an account definition.

  • If you are using automatic identity assignment, an associated identity is found and added to the user account when you save the user account.

  • If you create the user account manually, you can select an identity in the menu.

    The menu displays activated and deactivated identities by default. If you do not want to see any deactivated identities, set the QER | Person| HideDeactivatedIdentities configuration parameter.

NOTE: If you assign a deactivated identity to a user account, it might be locked or deleted depending on the configuration.

If an authentication object is assigned, the connected identity is found through the authentication object by using a template. If there is no authentication object assigned, the identity can be assigned automatically or manually.

You can create a new identity for a user account with an identity of type Organizational identity, Personalized administrator identity, Sponsored identity, Shared identity, or Service identity. To do this, click next to the input field and enter the required identity main data. Which login data is required depends on the selected identity type.

No link to an identity required

Specifies whether the user account is intentionally not assigned an identity.You can set the option manually. Enable the option if the user account does not need to be linked with an identity (for example, if several identities use the user account).

If attestation approves these user accounts, these user accounts will not be submitted for attestation in the future. In the Web Portal, user accounts that are not linked to an identity can be filtered according to various criteria.

Not linked to an identity

Indicates why the No link to an identity required option is enabled for this user account. The user account is not associated with an identity due to an exclusion criterion.

Site collection Site collection the user account is used in.
Group authenticated Specifies whether the user account's authentication object is a group.
Authentication objectClosed Authentication object referencing the user account. Each SharePoint user account represents an object from an authentication system trusted by the SharePoint installation. If this authentication system is managed as a target system in One Identity Manager, the SharePoint object used for authentication can be saved as the authentication object in the user policy.

The authentication object is assigned during automatic synchronization. You can assign an authentication object when setting up a new user account in the Manager. The authentication object cannot be changed after saving.

The following authentication objects can be assigned to a group authenticated user account:

  • Active Directory groups with the type "Security group" from the domain assigned to the farm or a trusted domain
  • LDAP groups from the domain assigned to the farm
Authentication modeClosed Authentication mode used for logging in on the SharePoint server with this user account.

The login name of new user accounts depends on the authentication mode. The authentication mode is set by a template. The value depends on the Claims-based authentication option of the associated web application. If you have defined custom authentication modes, select your authentication mode in the menu.

NOTE: Modify the template for this column (SPSUser.UID_SPSAuthSystem) to assign a custom authentication mode to user accounts.
Display name Any display name for the user account. By default, the display name is taken from the authentication object display name. Enter the display name by hand if no authentication object is assigned.
Login name User account login name. It is found using a template. Enter the login name by hand if no authentication object is assigned.
NOTE: Modify the template for this column (SPSUser.LoginName) to assign a custom authentication mode to user accounts.
Email address User account email address. It is formatted using templates from the authentication object's email address.

Risk index (calculated)

Maximum risk index value of all assigned SharePoint roles and groups. The property is only visible if the QER | CalculateRiskIndex configuration parameter is set. For more information, see the One Identity Manager Risk Assessment Administration Guide.

Category Categories for the inheritance of groups by the user account. Groups can be selectively inherited by user accounts. To do this, groups and user accounts or contacts are divided into categories. Select one or more categories from the menu.
Advice Text field for additional explanation.

Identity type

User account's identity type Permitted values are:

  • Primary identity: Identity's default user account.

  • Organizational identity: Secondary user account used for different roles in the organization, for example for subcontracts with other functional areas.

  • Personalized administrator identity: User account with administrative permissions, used by one identity.

  • Sponsored identity: User account to use for a specific purpose. Training, for example.

  • Shared identity: User account with administrative permissions, used by several identities. Assign all identities that use this user account.

  • Service identity: Service account.

Privileged user account. Specifies whether this is a privileged user account.
Administrator Specifies whether the user account is a site collection administrator.
Auditor Specifies whether the user account is a site collection auditor.
Detailed information about this topic

User authenticated user account main data

Enter the following main data of a user authenticated user account.

Table 21: User authenticated user account main data
Property Description
Identity

Identity that uses this user account.

  • An identity is already entered if the user account was generated by an account definition.

  • If you are using automatic identity assignment, an associated identity is found and added to the user account when you save the user account.

  • If you create the user account manually, you can select an identity in the menu.

    The menu displays activated and deactivated identities by default. If you do not want to see any deactivated identities, set the QER | Person| HideDeactivatedIdentities configuration parameter.

NOTE: If you assign a deactivated identity to a user account, it might be locked or deleted depending on the configuration.

If an authentication object is assigned, the connected identity is found through the authentication object by using a template. If there is no authentication object assigned, the identity can be assigned automatically or manually.

You can create a new identity for a user account with an identity of type Organizational identity, Personalized administrator identity, Sponsored identity, Shared identity, or Service identity. To do this, click next to the input field and enter the required identity main data. Which login data is required depends on the selected identity type.

No link to an identity required

Specifies whether the user account is intentionally not assigned an identity. The option is automatically set if a user account is included in the exclusion list for automatic identity assignment or a corresponding attestation is carried out. You can set the option manually. Enable the option if the user account does not need to be linked with an identity (for example, if several identities use the user account).

If attestation approves these user accounts, these user accounts will not be submitted for attestation in the future. In the Web Portal, user accounts that are not linked to an identity can be filtered according to various criteria.

Not linked to an identity

Indicates why the No link to an identity required option is enabled for this user account. Possible values:

  • By administrator: The option was set manually by the administrator.

  • By attestation: The user account was attested.

  • By exclusion criterion: The user account is not associated with an identity due to an exclusion criterion. For example, the user account is included in the exclude list for automatic identity assignment (configuration parameter PersonExcludeList).

Manage level Manage level of the user account. Select a manage level from the menu. You can only specify the manage level can if you have also entered an account definition. All manage levels of the selected account definition are available in the menu.

Account definition

Account definition through which the user account was created.

Use the account definition to automatically fill user account main data and to specify a manage level for the user account. One Identity Manager finds the IT operating data of the assigned identity and enters it in the corresponding fields in the user account.

NOTE: The account definition cannot be changed once the user account has been saved.

NOTE: Use the user account's Remove account definition task to reset the user account to Linked status. This removes the account definition from both the user account and the identity. The user account remains but is not managed by the account definition anymore. The task only removes account definitions that are directly assigned (XOrigin=1).

NOTE: If identities obtain their SharePoint user accounts through account definitions, the identities must own user accounts in the Active Directory domain or LDAP domain. This domain is stored in the SharePoint farm in which the SharePoint user accounts are to be created.
Site collection Site collection the user account is used in.
Group authenticated Specifies whether the user account's authentication object is a group. This option is disabled for user authenticated user accounts.
Authentication objectClosed Authentication object referencing the user account. Each SharePoint user account represents an object from an authentication system trusted by the SharePoint installation. If this authentication system is managed as a target system in One Identity Manager, the SharePoint object used for authentication can be saved as the authentication object in the user policy.

The authentication object is assigned during automatic synchronization. You can assign an authentication object when setting up a new user account in the Manager. The authentication object cannot be changed after saving.

The following authentication objects can be assigned to a user-authenticated user account:

  • Active Directory user accounts from the domain that is assigned to the farm or a trusted domain
  • LDAP user accounts from the domain assigned to the farm

User accounts that refer to the default SIDs of an Active Directory environment cannot reference an authentication object in One Identity Manager.

NOTE: The SharePoint user account is also created if the user account that is used as the authentication object is disabled or locked.
Authentication modeClosed Authentication mode used for logging in on the SharePoint server with this user account.

The login name of new user accounts depends on the authentication mode. The authentication mode is set by a template. The value depends on the Claims-based authentication option of the associated web application. If you have defined custom authentication modes, select your authentication mode in the menu.

NOTE: Modify the template for this column (SPSUser.UID_SPSAuthSystem) to assign a custom authentication mode to user accounts.
Display name Any display name for the user account. By default, the display name is taken from the authentication object display name. Enter the display name by hand if no authentication object is assigned.
Login name

User account login name. It is found using a template. Enter the login name by hand if no authentication object is assigned.

NOTE: Modify the template for this column (SPSUser.LoginName) to assign a custom authentication mode to user accounts.
Email address User account email address. It is formatted using templates from the authentication object's email address.

Risk index (calculated)

Maximum risk index value of all assigned SharePoint roles and groups. The property is only visible if the QER | CalculateRiskIndex configuration parameter is set. For more information, see the One Identity Manager Risk Assessment Administration Guide.

Category Categories for the inheritance of groups by the user account. Groups can be selectively inherited by user accounts. To do this, groups and user accounts or contacts are divided into categories. Select one or more categories from the menu.
Advice Text field for additional explanation.

Identity type

User account's identity type Permitted values are:

  • Primary identity: Identity's default user account.

  • Organizational identity: Secondary user account used for different roles in the organization, for example for subcontracts with other functional areas.

  • Personalized administrator identity: User account with administrative permissions, used by one identity.

  • Sponsored identity: User account to use for a specific purpose. Training, for example.

  • Shared identity: User account with administrative permissions, used by several identities. Assign all identities that use this user account.

  • Service identity: Service account.

Privileged user account. Specifies whether this is a privileged user account.

Groups can be inherited

Specifies whether the user account can inherit groups through the linked identity. If the option is set, the user account inherits groups through hierarchical roles, in which the identity is a member, or through IT Shop requests.

  • If you add an identity with a user account to a department, for example, and you have assigned groups to this department, the user account inherits these groups.

  • If an identity has requested group membership in the IT Shop and the request is granted approval, the identity's user account only inherits the group if the option is set.

Roles can be inherited

Specifies whether the user account can inherit SharePoint roles through the linked identity. If the option is set, the user account inherits the roles through hierarchical roles, in which the identity is a member, or through IT Shop requests.

Administrator Specifies whether the user account is a site collection administrator.
Auditor Specifies whether the user account is a site collection auditor.
Detailed information about this topic
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택