Identity Manager 8.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 SharePointSite 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 Site Collections Appendix: Configuration parameters for managing a SharePoint environment Appendix: Default Project Template for SharePoint

Additional Tasks for Managing Sites

After you have entered the master data, you can apply different tasks to it. The task view contains different forms with which 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 Open URL 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 SharePoint | Sites.
  2. Select the site in the result list.
  3. Select SharePoint site overview.
Related Topics

Child Sites Inheriting Permissions

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. Unique role definition specifies whether a site inherits roles from the parent site. Unique role assignment 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, UID_SPSPrefix and UID_SPSWebTemplate are provided for the table SPSWeb 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 in 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 table PersonWantsOrg 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 in 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 employees managed in One Identity Manager. One Identity Manager makes it possible for you to obtain an overview of all an employee'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. Clara Harris owns an Active Directory user account, which is a member in this group. She can log in to the site collection with this and obtain all the SharePoint user account's permissions.

Jan Bloggs is also requires guest access to the site collection. He owns an Active Directory user account in the same domain. He request membership of the Web Portal group in Active Directory. Once the request is granted approval and assigned, he 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 employee. This means, the user account can only become a member in SharePoint roles and groups through direct assignment.
  • In order for an employee 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 employee. This means that the user account can become a member in SharePointroles and groups through inheritance and direct assignment.

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

    If there is no authentication object assigned, the employee can be assigned automatically or manually. Automatic employee assignment depends on "TargetSystem\SharePoint\PersonAutoFullsync" and "TargetSystem\SharePoint\PersonAutoDefault".

  • 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 employee. This means that the user account can become a member in SharePoint roles and groups through inheritance and direct assignment. Automatic employee assignment depends on "TargetSystem\SharePoint\PersonAutoFullsync" and "TargetSystem\SharePoint\PersonAutoDefault".
  • 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 SPSUser.LoginName and SPSUSer.DisplayName.
  • The user account can be managed through an account definition.

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

Related Documents