Stop MongoDB connector in case of authorization failure

If a command of the MongoDB connector fails (e.g. retrieval of all collections), the operation is repeated indefinitely.

This might warrant a more general reconsideration, but at least in the case of authorization failures (which are generally not unexpected) it seems more appropriate to propagate the exception, causing the connector to be stopped. Currently, the logs are flooded with the same exception over and over again.