If you have a runtime exception happening when using a REST endpoint, this exception may not be printed in any logs.
Therefore, you can end with a 500 from the client side but no trace of it in the server side.
The main problem is that our CREST chain in OpenAM doesn't have a RunTimeException handler.
We should had one that print the exception in the logs.
How to reproduce the issue
I faced this issue when testing a sample custom authentication module, which has a missing property.
For saving times, I would suggest reproducing the problem in an existant module.
- Copy the amAuthLDAP.properties into WEB-INF/classes
- Remove the property "a500=Authentication Level"
- Go the console and try to edit the LDAP configuration
=> you will have a "Not found error."
If you look the request made by the XUI, you will see that the request
returns a 500.