FileNet Content Manager 5.2.1: security (F283G)

• Tickets come in saying “I cannot see this document” and get solved by trial and error.
• Permissions have been set by hand over years and nobody knows any more why they are like that.
• A new department needs access without opening the whole repository to it.

• Resolve access issues: security in the FileNet P8 domain, authentication and authorization, security principals, users and groups, security realms, the Content Navigator desktop and login errors
• Modify direct security: permissions, security sources and their order of evaluation, what direct security is, access control from Content Navigator and from the Administration Console, permission groups and ownership
• Configure object store security: required accounts, administrators and users, an example security scenario, the initial configuration, super groups, the Security Script Wizard and root folder security
• Configure class and property security: default instance security and how to set it, property modification security, configuring modification access and system property modification
• Configure security inheritance: what it is, its architecture, the characteristics of inherited permissions, the methods for configuring it, using a security folder and using an object as a security proxy

• Labs on the permissions of a real system: identifying access issues, modifying direct security from the console and from Content Navigator, and configuring inheritance with a security folder and with an object as proxy.
• Taught directly by IBM Champion instructors from the SIXE team.
• Credly badges on completion: credly.com/organizations/sixe/badges
• Flexible format — online, classroom or onsite — in closed groups, priced per attendee, in the language of your choice (ES / EN / FR).

Why so much weight on inheritance?
Because it produces the cases nobody understands: a permission that is not on the document but on the folder, or on an object acting as a proxy. Seeing the inheritance methods in order is what turns those tickets into something diagnosable.

Is the order permissions are evaluated in covered?
Yes: the security sources are covered in their order of evaluation, which is what explains why two permissions that contradict each other look like a product bug when they are the expected behaviour.

Can we bring a permissions case of our own?
Yes, and it tends to be the most useful part: we take a real ticket of yours — a user who cannot see a document they should — and diagnose it in class, layer by layer, until we find where the permission comes from.

Can you deliver it at our premises?
Yes, and remotely with a live instructor too. Closed groups of four to ten people, in Spanish, English or French.

• F281G — building the repository
• F282G — object metadata
• F288G — full administration