Chat now with support
Chat with Support

Identity Manager 9.2 - 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

Additional tasks for managing sites

After you have entered the main data, you can run the following tasks.

You can view all the roles and permission levels that are valid for this site on the overview form. Use the Open URL task to open the site in a standard web browser. Prerequisite for this is that the server in the URL can be resolved per DNS.

To obtain an overview of an site

  1. Select the SharePoint > Sites category.
  2. Select the site in the result list.
  3. Select the SharePoint site overview task.
Related topics

Passing on permissions to child sites

SharePoint roles are defined at site level. There are always roles defined for the root site of a site collection. Child sites can inherit these role definitions. In the same way, roles on the root site of a site collection are also assigned to groups or user accounts. These assignments can inherit child sites. The Unique role definition option specifies whether a site inherits roles from the parent site. The Unique role assignment option specifies whether user accounts and groups are explicitly authorized for a site or whether the role assignments are inherited by the parent website.

Detailed information about this topic
Related topics

Setting up SharePoint site collections and sites

Site collections and sites are simply loaded into the One Identity Manager database through synchronization in the default installation of One Identity Manager. You can add new site collections and site in the One Identity Manager and publish them in the SharePoint target system. To do this, the UID_SPSPrefix and UID_SPSWebTemplate columns are provided for the SPSWeb table as well as predefined scripts and processes.

NOTE: You can use the following scripts and processes to request site collections and sites from the IT Shop. Customize these scripts and processes as required!
Script/Process Description
Script VI_CreateSPSSite Creates a new site collection and the associate root site in the One Identity Manager database. Creates a user account that is entered as site collection administrator or root site author.
Script VI_CreateSPSWeb Creates a new site within a site collection in the One Identity Manager database.
Process SP0_SPWeb_(De-)Provision Creates a new site within a site collection. The process is triggered by the event PROVISION when the site in the One Identity Manager database is not labeled as the root site.
Process SP0_SPSite_(De-)Provision Creates a new site collection in a web application and the associated root site. The process is triggered by the event PROVISION.

The following step are required in additions:

  • Define a requestable product through which the site collection/site is requested from the IT Shop.
  • Define product properties that are mapped to the script parameter (for example web application, prefix, or site template). You must include these product properties when the site collection/site is requested.
  • Create a process for the PersonWantsOrg table that is started when the request is approved (event OrderGranted). This process call the matching script and sets the parameter values with the defined product properties you have defined. Then the site collection/site is added to the One Identity Manager database.

SharePoint user accounts

SharePoint user accounts provide the information necessary for user authentication, such as, the authentication mode and login names. In addition, permissions of users in a site collection are specified in the user accounts.

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. This means the SharePoint user account permissions are mapped to identities managed in One Identity Manager. One Identity Manager makes it possible for you to obtain an overview of all an identity's SharePoint access permissions. SharePoint permissions can be attested and checked for compliance. Employees can request or obtain the SharePoint permissions they requires through their memberships in hierarchical roles or through the Web Portal when appropriately configured.

Example

Set up guest access to a site collection with read-only permissions. To do this, a SharePoint user account is added. The Active Directory group "Guests" is assigned as authentication object to the user account. Jo User1 owns an Active Directory user account, which is a member in this group. They can log in to the site collection with this and obtain all the SharePoint user account's permissions.

Jan User3 also obtain a guest login for the site collection. They own an Active Directory user account in the same domain. They request membership of the Web Portal group in Active Directory. Once the request is granted approval and assigned, they can log in on the site collection.

By default, the following objects can be assigned as authentication objects in One Identity Manager.

  • Active Directory groups (ADSGroup)
  • Active Directory user accounts (ADSAccount)
  • LDAP groups (LDAPGroup)
  • LDAP user accounts (LDAPAccount)

During synchronization, One Identity Manager tries to assign the matching authentication object using the login name.

SharePoint access permissions are supplied in different ways in the One Identity Manager, depending on the referenced authentication object.

Case 1: The associated authentication object is a group. The authentication system is managed in One Identity Manager. (Default case)
  • The user account represents an Active Directory or LDAP group. This group can be assigned in the One Identity Manager as authentication object.
  • The user account cannot be assigned to an identity. This means, the user account can only become a member in SharePoint roles and groups through direct assignment.
  • In order for an identity to log in on the SharePoint system, they require an Active Directory or LDAP user account. This user account must be member in the Active Directory or LDAP group.
  • A new SharePoint user account can be created manually.
  • The user account cannot be managed through an account definition.
Case 2: The authentication object is a user account. The authentication system is managed in One Identity Manager.
  • The user account represents an Active Directory or LDAP user account. The user account is not assigned as an authentication object in One Identity Manager.
  • The SharePoint user account can be assigned to an identity. This means that the user account can become a member in SharePoint roles and groups through inheritance and direct assignment.

    If an authentication object is assigned, the connected identity is found through the authentication object.

    If there is no authentication object assigned, the identity can be assigned automatically or manually. Automatic identity assignment depends on the TargetSystem | SharePoint | PersonAutoFullsync and TargetSystem | SharePoint | PersonAutoDefault configuration parameters.

  • A new SharePoint user account can be manually created or by using an account definition. The Active Directory or LDAP user account used as authentication object must belong to a domain trusted by the referenced authentication system.
  • The user account can be managed through an account definition.
Case 3: The authentication object is a user account. The authentication system is not managed in One Identity Manager.
  • The user account cannot be assigned an authentication object.
  • The user account can be manually or automatically assigned to an identity. This means that the user account can become a member in SharePoint roles and groups through inheritance and direct assignment. Automatic identity assignment depends on the TargetSystem | SharePoint | PersonAutoFullsync and TargetSystem | SharePoint | PersonAutoDefault configuration parameters.
  • A new SharePoint user account can be manually created or by using an account definition. If an account definition is used, the column templates must be customized for the SPSUser.LoginName and SPSUSer.DisplayName columns.
  • The user account can be managed through an account definition.

The basics for managing identities and user account are described in the One Identity Manager Target System Base Module Administration Guide.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating