AM allows invalid metadata to be loaded to an entity. When accessing the same entity through the console, the user is redirected to https://am.example.com:8443/openam/console/base/AMUncaughtException and a 'Not Found' message is displayed on a blank page.
The debug logs print the following:
- Deploy vanilla AM 6.5.2
- Create a SAML entity provider
- Provide metadata with an empty SingleLogoutService object and an AssertionConsumerService object with no index (see attachment)
- In the AM console, browse to the entity in question - you won't be able to see its details