PingIDM

Embedded Jetty configuration

In IDM 7.5.1 and later, the embedded Jetty web server supports Jetty 12.

When serving SSL requests, Jetty 12 checks that the incoming host header matches the server certificate’s subject and returns a 400 Bad Request error on a mismatch. If you’re upgrading to IDM 7.5.1 or later, you must ensure your IDM server certificate subject matches the host name used by your deployment.

Learn more in What’s new.

IDM includes an embedded Jetty web server.

To configure the embedded Jetty server, edit openidm/conf/jetty.xml. IDM delegates most of the connector configuration to jetty.xml. OSGi and PAX web specific settings for connector configuration therefore do not have an effect. This lets you take advantage of all Jetty capabilities, as the web server is not configured through an abstraction that might limit some options.

The Jetty configuration can reference configuration properties (such as port numbers and keystore details) from your resolver/boot.properties file.