You must install the Policy Editor and the PingAuthorize server before enabling Camel services.

To ensure that Camel is used with appropriate permissions and security controls, Camel services are disabled by default in the Policy Editor. Starting with version 10.0, you can use Camel version 3.21.2. Learn how to upgrade PingAuthorize versions 9.3 and earlier using Camel 2.x in the Apache Camel 2.x to 3.0 migration guide.

Warning:

If you upgrade an existing installation of PingAuthorize to version 9.3.0.0 or later, and the earlier version was configured in embedded PPD mode with a deployment package containing Camel services, the upgraded PingAuthorize server will fail to start. The following steps also resolve this issue:

  1. In the PingAuthorize server distribution, copy the symphonic-camel-pdp-<version>.jar file from resource/camel to the lib folder.
  2. In the Policy Editor distribution, copy the symphonic-camel-pap-<version>.jar file from resource/camel to the admin-point-application/lib folder.
  3. Enable the Camel service.
    • Run setup in non-interactive mode using the --enableCamelService argument.
      $ bin/setup demo \
--adminUsername admin \
--generateSelfSignedCertificate \
--decisionPointSharedSecret pingauthorize \
--hostname <pap-hostname> \
--port <pap-port> \
--adminPort <admin-port> \
--licenseKeyFile <path-to-license> \
--optionsFile my-options.yml \
--enableCamelService
      Warning:

      This choice will override the existing configuration.

    • In your Policy Editor distribution, add the - "camel-service" flag to enabledFeatures in the config/configuration.yml file.
      enabledFeatures:
- "test-suite"
- "entity-dependents"
- "camel-service"
  4. Save your changes and restart the Policy Editor.

Camel service connections are enabled in both external and embedded PDP modes.