The Directory area is accessible using the icon at the bottom of the left browser of the Archive Portal administration module. It contains the data present in the Access.xml and Directory.xml files. This data is used to secure access to the Archive Portal (Login) and access to databases (Notes identities present in the ACL) and to Notes documents (Notes identities present in the Readers fields). The area is divided into 3 tabs:

• Portal Users: List of Active Directory users allowed to connect to the Archive Portal.
• Directory Person: List of Domino directory Persons.
• Directory Group: List of Domino Directory Groups.

The Access.xml and Directory.xml files are automatically built from the Identity Station of the Application Migration Factory installed on one of the company's Domino servers. If the Domino infrastructure is still present alongside the Archive Portal, the Access.xml and Directory.xml files will be automatically generated and deployed to the Archive Portal at regular intervals. You should therefore not try to modify them on the Archive Portal side as any modifications would be overwritten during the next file update. If you want to make changes, make them from the Identity Station database, and they will be pushed into the Access.xml and Directory.xml files when they are deployed.

If the Domino infrastructure has been stopped, updating access and authorizations must be done from the Directory area tabs. You can create new users and modify or delete existing ones. You can also create Notes identities and manage group membership.

If a user cannot connect to the Archive Portal, first check that their login appears in the Portal Users tab. If he doesn't see any databases icons on workspace, check the Notes identity (FullName) associated with its login. You will then need to analyze the ACL of the database to check if one of its Notes identities (or the groups to which it belongs) is indeed present, with at least Reader access level. If a user doesn't see one document in a Notes databases, check the Reader fields section (<SECURITY><READ>) in the XML file of the document. You should find there one of the Notes identities of the user (or one of its groups to which he belongs). If the section is empty, the document is public (accessible to everyone).

Portal Users Tab

The Portal Users tab displays the data present in the Access.xml file:

Every user authorized to log in to the archive portal must have an entry in the Access.xml file. We find there his connection identifier (Active Directory login), his associated FullName Notes (identity) as well as his Portal access privileges (Administrator or Security Officer):

You can create/modify/delete Users entries using the Create, Modify and Delete buttons present at the top right of the Portal Users tab. A User entry contains 4 fields:

• • • Login: Login identity (Active Directory) of the user.
    • Full Name: FullName Notes associated with this user.
    • Is Admin: Indicates whether this user has Archive Portal administration privileges.
    • Security Officer: Indicates whether this user has security officer privileges.

You can set FullName using the Notes identities icon which will open the Person selection window:

Directory Persons Tab

The Directory Persons tab displays the Person data present in the Directory.xml file:

All users present in the address book of the Domino infrastructure (from which the hosted databases come) are added in the Directory.xml file, in the form of <PERSON> entries:

There we find the Notes fields of the NAB Person file (FirstName, Last Name, FullName, Shortname, InternetAddress) as well as the list of groups to which this user belongs.

You can create/edit/delete Persons entries using the Create, Modify and Delete buttons present at the top right of the Directory Persons tab. A Person entry contains 5 fields:

• • • Last Name: User last name.
    • First Name: User first name.
    • Full Name: FullName Notes associated with this user (main identity linked to the User file).
    • Extra Identities: Other identities of this person (usable in the readers field or ACL).
    • Group Membership: List of Notes Groups to which this user is member of.

You can define the list of groups using the Notes identities icon which will open the Groups selection window:

You can select multiple group names and associate them with the Domino user using the Add button.

Directory Groups Tab

The Directory Groups tab displays the Group data present in the Directory.xml file:

All the groups present in the address book of the Domino infrastructure (from which the hosted databases come) are added in the Directory.xml file, directly declared in the <PERSON> entries or as <GROUP> entries:

You can create/modify/delete Groups entries using the Create, Modify and Delete buttons present at the top right of the Directory Groups tab. A Group entry contains only 1 field:

• • • Group Name: Name of the group.

Unlike the Domino address book where group entries contain the identities of their members, the logic is reversed in the Archive Portal. It is the Person entry which contains the list of groups to which the user is attached. The Group entry is therefore empty, it is only used to define the name of the Group which will then be selectable from a Person record.