Skip navigation FileNet logo
Glossary  |  Help Directory  
  Help for Process Engine Reference  
  Search  |  Index  
Concepts
  About attachments
  About the Component Integrator
  About launching a workflow
  About milestones
  About operations
About the RMI registry
About rosters
About routing
About rules
  About security
  About security queues
  About step processors
  About step states
  About system maps
  About transfer
  About workflow fields
  About workflow maps
  About workflow participants
  Component queue security issues
  Content Engine (CE) operations
  Coordinate information
  Custom web applications
  Eliminating port 32771 conflicts
  Java Runtime Environment (JRE)
  Maximum index key size
  Naming conventions
  System fields
  Troubleshooting
  Wildcards
  Workflow database field size limitations
  Workflow exceptions
Events & Statistics
Expressions
Procedures
   

Component Integrator security issues

The Component Integrator makes it possible to access an external entity, such as a Java object or (Workplace only) Java messaging system (JMS), from a step in a workflow. For example, via the Component Integrator a workflow could:

  • Run a component that accesses some external data, such as a payroll system.
  • (Workplace only) Execute a FileNet-provided Content Engine (CE) operation function that changes the properties of a document in an object store.

Components are defined within an isolated region and can be used in any workflow defined within the isolated region. So that a component behaves consistently from workflow to workflow, the permissions a component has on the specific entity it interacts with are also defined at an isolated region level. For example, the CE operations have the necessary permissions to get and set document properties, file and unfile a document in a folder, and publish a document. So, if the CE Operation that publishes a document is used in both workflow A and workflow B, when the step containing that component is completed in either workflow, a document will be published.

Because a component's permissions on an entity might exceed those that the user running the workflow has on that entity, FileNet recommends that you limit access to workflows that contain component steps, in order to protect the external systems.

The following table summarizes the various security issues, and provides recommendations to help you provide security for external systems accessed by component steps.

Issue Recommendation
Anyone who can create a workflow can include a pre-defined component that has specific access to whatever entity the component interacts with. In Workplace, by defining a workflow that contains the appropriate CE operations, for example, a user can ultimately make changes to a document to which he personally doesn't have Modify access.
  • Limit access to the Process Designer application. See Application security for further instructions.
  • Limit access to secure documents that might be targeted for unauthorized changes using CE operations. (A workflow designer who has View access to a document can specify that document as a parameter to a CE operation that changes his access level.).
Anyone who can launch a workflow can initiate the action performed by the workflow component step.
  • Limit access to workflow definitions that contain component steps.
  • Limit access to documents with a workflow subscription (Workplace) or a workflow that is launched automatically (FileNet Web Services Client or Open Client) that contains component steps.