Catch bad user name/ password (non ZK) on connect in Fabric Explorer instead of a bad authentication later on.

I'm having trouble triggering the data access fault for "Local Fabric"

Are we sure it's a bug that a bad user-id/user-password and good zooKeeper password is not being
reported as an error?

The problem here is that it can cause great deal of confusion, when the user connect to Fabric successfully and later on he fails to do things, like creating containers, deploying artifacts to fabric, or sshing to containers due to the "bad credentials" he specified when connecting.

I am not sure if the fabric jaas realms, are deployed in the IDE land. If they are, then you may be able to perform a simple login using the provided credentials for validation purposes. If they are no, then maybe you could just try to connect via jmx to any of the containers in fabric.

If none of the above is really an option, then you could just catch those errors when thrown (creating containers, deploying, connecting via ssh/jmx) and prompt the user again for credentials.