[NETCONF-665] Differentiate authentication failures from other session setup failures Created: 17/Apr/20 Updated: 21/Apr/20 Resolved: 21/Apr/20 |
|
| Status: | Resolved |
| Project: | netconf |
| Component/s: | netconf |
| Affects Version/s: | None |
| Fix Version/s: | Magnesium SR1, Aluminium, Sodium SR3 |
| Type: | Improvement | Priority: | Medium |
| Reporter: | Robert Varga | Assignee: | Robert Varga |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
We provide a programmatic way of establishing netconf sessions, but for failure paths we do not differentiate between the various modes of failure. Specifically it is hard to discern when a connection fails due to authentication issue, and downstreams have to rely on parsing our error message to find that out. Provide well-defined exception types to handle the various root causes of failures based on their source domain (transport, auth, etc.) |