Unified Automation Forum

Session.Connect() supports automatic retrying when a failure is encountered. However, this retry behavior is not performed when certificate errors are encountered.

We prompt our users to trust certificates when this occurs. To simplify the user experience, we want to automatically retry connections after certificate errors. We can implement this retrying ourselves, but it would be preferable if the Session.Connect() handled it for us like it does with other kinds of errors.

Hi,

the automatic reconnect has two fold approach: distinguishing between errors which occur "initially" (on first connect) and which occur "later" during operation (but was working initially). Furthermore a decision has to be made on non-recoverable errors (makes no sense to reconnect) and recoverable errors (we hope that it will work on next retry). The idea is to stop when the user has made a configuration error, or in case some user interaction is required to recover.

The not existing "trust" is seen as "non-recoverable", because admin must come and do something (verify cert, and trust) before we can continue. Howerver, I aggree that "try again and hope for the best" may also be a valid use case (i.e. when having GDS in the loop that pushes new trust list).