[BUG] Connector shutdown upon configuration file error unexpectedly causes subsequent session revocation error(s)

[alexjhawk]

Do I have the latest version of the Ewon firmware?

• Yes

Do I have the latest version of the application?

• Yes

Do I have a custom or modified version of the application?

No

Ewon Firmware Version

14.8s0

Application Version

1.0.2

Network Connection Type

Ethernet

Current Behavior

Upon connector startup without a complete URL/username/password configuration, a shutdown is properly invoked as expected. During the invoked shutdown, though, one or several errors may be thrown due to the failure to clean up session tokens, etc.

Expected Behavior

During the invoked shutdown (resulting from an incomplete URL/username/password configuration), these errors should be suppressed, or the session token revocation should be bypassed.

Steps to Reproduce

Enable/run the connector with a proper configuration file but default username and password configuration values:

Additional Information

If a configuration file error triggers a shutdown, there is likely no session token generated or able to be generated.

This means that calling the session revocation process will likely fail because either 1) no session token exists to revoke or 2) a session token revocation request cannot be properly formed.

Code of Conduct

• I agree to abide by the Code of Conduct.