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 the task 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
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 option Unique role definition specifies whether a site inherits roles from the parent site. The option 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.
Site collections and sites are simply loaded into the One Identity Manager database through synchronization in the default installation of the 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 columns 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:
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. Thus, 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 a 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 a 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 the One Identity Manager.
During synchronization, the 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.
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 the configuration parameters "TargetSystem\SharePoint\PersonAutoFullsync" and "TargetSystem\SharePoint\PersonAutoDefault".
The basics for managing employees and user account are described in the One Identity Manager Target SystemAn instance of a target system in which the employees managed by One Identity Manager have access to network resources. Example: An Active Directory domain X for target system type "Active Directory", a directory Y for target system type "LDAP", a client Z for target system type "SAP R/3". Base Module Administration Guide.
© 2021 One Identity LLC. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy