This mechanism in all management cases has previously been hard coded to be quiet by default, the is the predominant usage of the mechanism.

For a couple of EJB edge cases which have been found in the test suite we are putting in a lot of effort to keep it interactive by default.

If we don't make it quiet by default we are going to require either a wildfly-config.xml for each management client which is something we are trying to avoid or each management client is going to require access to the mechanism properties from the authentication configuration so they can be safely manipulated.