Geotab API does not throw error when calling Authenticate with incorrect sessionId

[Naragod]

import GeotabAPI = require("mg-api-js");
const api = new GeotabAPI(authentication, options);
// this call does not throw an error if the sessionId used is expired, or incorrect
api.authenticate()

When authenticating using the geotab client, we are running into errors during the execution of individual calls, rather than during the original authentication process.

Having it fail when calling authenticate would allows to fail first and early if the sessionId is incorrect.

[minusInfinite]

I know its is a from a few years ago, but for anyone else having this confusion see the line api.authenticate() currently doesn't use sessionId, only password. If you Auth object has only a sessionId you should use api.getSession() instead and if auth fails due to the session being expired it should then trigger password auth.