https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/AAA-109 aaa <p>Typical case is in High Availability testing. One cluster member has been rebooted and it is starting again. Not every AAA bundle is ready, so restconf returns 401.</p> <p>In reality, the user probably is allowed to access the resource, so 401 may be misleading. Restconf could wait until AAA is ready (or a timeout expires).</p> <p>Setting severity to minor, as this only happens shortly after boot, and it may not be easy to figure out when exactly AAA becomes ready.</p> <p>It is possible that AAA project has authority on HTTP processing at this stage, in which case this is a AAA Improvement.</p> <p>Operating System: All<br/> Platform: All</p> AAA-109

When it is known some features have not activated fully, do not return 401

Bug Resolved Done Unassigned Vratko Polak Wed, 21 Sep 2016 13:32:11 +0000 Thu, 21 Mar 2019 11:56:46 +0000 Thu, 14 Sep 2017 17:17:49 +0000 General 0 3 <p>It is how you mentioned. This should be in AAA project.</p> <p>Still present (Carbon snapshot).</p> <p>There are more specific Bugs (soon to be) open, differing on reason of why a feature is not activated yet.<br/> Generally, the correct HTTP status code should be 503 (assuming AAA authorizes the caller, otherwise 401 is ok).</p> <p>This might be resolved now due to 8214; a service was exposed and NETCONF (RESTCONF really) now consumes the service. Have you seen this recently, or can we close this?</p> Development External References netconf_cluster_stress_txt_topology_leader_ha_stop_configurer External issue ID 6772 External issue URL Issue Type ODL SR Target Milestone Rank 0|i0245j: