At https://github.com/twingly/ecco/blob/v0.5.0/lib/ecco/client.rb#L49 we rescue `IOException`, and always return `Ecco::Error::ConnectionError`, but we could improve that and return different errors for different situations. mysql-binlog-connector-java has [AuthenticationException](https://github.com/shyiko/mysql-binlog-connector-java/blob/0.2.4/src/main/java/com/github/shyiko/mysql/binlog/network/AuthenticationException.java) that inherits from [ServerException](https://github.com/shyiko/mysql-binlog-connector-java/blob/0.2.4/src/main/java/com/github/shyiko/mysql/binlog/network/ServerException.java) that inherits IOException. At https://github.com/twingly/ecco/blob/v0.5.0/spec/integration/client_spec.rb#L273 we could expect the authentication error I think.
At https://github.com/twingly/ecco/blob/v0.5.0/lib/ecco/client.rb#L49 we rescue
IOException, and always returnEcco::Error::ConnectionError, but we could improve that and return different errors for different situations.mysql-binlog-connector-java has AuthenticationException that inherits from ServerException that inherits IOException.
At https://github.com/twingly/ecco/blob/v0.5.0/spec/integration/client_spec.rb#L273 we could expect the authentication error I think.