"Neo.ClientError.Security.Unauthorized": Driver does not retry authentication after transient failure

Goal: Determine whether an application should implement its own retry logic when the Neo4j Bolt driver returns Neo.ClientError.Security.Unauthorized due to a temporary authentication glitch.

Constraint: The driver treats this error as non‑retryable and does not retry the authentication exchange, even if the underlying TCP connection is reconnected.

Uncertainty: Documentation does not clarify if brief server overload or momentary auth‑service unavailability can cause a recoverable Unauthorized error, leaving integrators to decide on a retry strategy.

Questions: Should the application retry session creation after receiving Neo.ClientError.Security.Unauthorized? What observable signs indicate a transient versus permanent credential failure? How many retry attempts, if any, are safe without risking lockout?