Secondary Configurations in the OpenAM console are not possible to save in OpenAM 14.0.0, as they are sending an escaped json string rather than a json object.
For example creating an audit log handler sends the initial payload of
which is a valid JSON configuration. Updating it then sends
As a result the response from the update is HTTP-400 (Bad Request) "The request could not be processed because the provided content is not a JSON object"
- Log into OpenAM as amadmin
- Navigate to Configure -> Global Configuration -> Audit Logging -> Secondary Configurations -> Global JSON Handler
- Click Save
HTTP-400 and error message.
This happens for all secondary configuration instances, including
- RADIUS server
It is also happens for realm configuration, as well as global.