The issue with the Authentication status as mentioned in the Pivotal story (link below) was first isolated to a single controller action that fails. The controller action at first could not be called in my setup (caused by a faulty config). And I wanted to ensure this was not due to Symfony unable to evaluate which action to render. I moved off all other actions to a controller of its own. So this was kind of a boyscout action.
I then fixed the actual fault in my own setup (the config issue I mentioned above). And upgraded the error reporting of the Assertions performed in the TiqrConfiguration. Again boyscout work
Finally, when the authn call fails for some reason. The Authn status action will now return a error response that can be dealt with by the JS app. Previously the 500 errror page was returned. It now sends back a generic error response. Which is picked up by the JS app which displays the user friendly error page
See: https://www.pivotaltracker.com/story/show/188205289