Allow Additional Classes For Processing
Overview
Sometimes your integration may use custom objects or third-party libraries that are not recognized by OpsHub Integration Manager by default. When this happens, the integration can fail with error:
com.thoughtworks.xstream.security.ForbiddenClassExceptionYou can configure the allowed.xstream.classes property to explicitly authorize trusted classes or packages that are required for your integration to work correctly.
Only allow classes or packages from trusted sources.
Availability
This configuration is supported from OpsHub Integration Manager version 7.234 onwards.
When to Use This Property
Configure allowed.xstream.classes only when:
Your integration relies on a third-party library that is not included in OpsHub Integration Manager's default allow list.
An integration job fails with a
com.thoughtworks.xstream.security.ForbiddenClassExceptionerror.You have reviewed the blocked class and confirmed it is from a trusted source.
Applying the Configuration
Stop the OpsHub Integration Manager server.
Go to <OpsHub Integration Manager Installation Path>/AppData/OpsHubData
Open the
OIM_Config.propertiesfile.Add or update the
allowed.xstream.classesproperty with the required values. (Check the Sample Scenario section to know more.)Save the file.
Restart the OpsHub Integration Manager server.
Sample Scenario
A custom connector uses objects from the Apache Commons library. During synchronization, OpsHub Integration Manager blocks the object because it is not part of the default trusted list. By adding the required class or package to the allowed.xstream.classes property, OpsHub Integration Manager can process the data successfully and the integration continues without errors.
Below are the samples of how the allowed.xstream.classes property value can be set:
Allow Specific Classes
Allow an Entire Package Hierarchy
Allow Multiple Classes and Packages
Last updated