Oracle WebCenter Interaction Administrator Guide

     Previous Next  Open TOC in new window   View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Example of Importing Security

Assume that you create an authentication source called myAuthSource importing users and groups into the portal from a source domain called myDomain. This authentication source uses the category Employees. Therefore, the text "Employees\" is prepended to each user's name and each group's name to distinguish these users and groups from those imported through other authentication sources. For example, if you have a user myDomain\Mary in the source domain, the user is imported into the portal as Employees\Mary.

Every authentication source automatically creates a group that includes all the users imported through that authentication source. In this example, because the authentication source is called myAuthSource, the group that includes all imported users is called Everyone in myAuthSource.

Suppose that you want to import content from a Lotus Notes system called myNotes, which includes users and groups equivalent to those found in the myDomain domain. Because you have already imported these groups and users into the portal, your Notes content crawler can import Notes security information along with each Notes document. The groups in the Notes system do not have to have the same names as their corresponding groups in the myDomain domain or in the portal; the important thing is that there are Notes groups that have equivalent portal groups. If there are Notes groups that do not have equivalent groups in the portal, your Notes content crawler will ignore security settings referring to such groups.

When your Notes content crawler finds a document, it creates a list of the Notes groups that have access to it. This list is called an ACL (Access Control List). The ACLs created for Notes documents do not contain entries for specific Notes users, only for Notes groups. (Notes content crawlers only grant access to portal groups. Windows File content crawlers do grant access to portal users.) Each ACL entry is written as {Notes Server Name}\{Notes Group Name}. In this example, the content crawler creates an ACL with the single entry myNotes\Engineering, because this is the only Notes group that has access to that document.

The content crawler then refers to the Global ACL Sync Map to determine which portal group corresponds to this Notes group. This is a two-stage process:
  1. Knowing that you would import documents and security through Notes content crawlers, on the Prefix: Domain Map page, you mapped the myAuthSource category Employees to the source domain myNotes. Guided by this entry, your content crawler modifies the ACL entry from myNotes\Engineering to Employees\Engineering.
  2. Knowing that your Notes system uses a different group name than your myDomain domain, on the Portal: External Group Map page, you mapped the Notes system group Engineering to the myDomain group, now, the portal group, Developers. Guided by this entry, your content crawler modifies the ACL entry from Employees\Engineering to Employees\Developers.
As a result, all the users in the portal group Developers are automatically granted access to the document.

  Back to Top      Previous Next