topic Re: Prime Infrastructure v2.2 REST API 401 Unauthorized error in Controllers https://community.cisco.com/t5/controllers/prime-infrastructure-v2-2-rest-api-401-unauthorized-error/m-p/3472481#M1228 <HTML><HEAD></HEAD><BODY><P>If you're seeing intermittent 401 errors, there are two probable causes.</P><P></P><P>First, check to make sure that you're not using persistent connections (which means sending the "Connection: keep-alive" header).&nbsp; Many clients will use persistent connections by default.&nbsp; You can either disable the persistent connection option in your client, or send the "Connection: close" header.&nbsp; See the <A href="https://developer.cisco.com/media/prime-infrastructure-api-reference-v3-0/192.168.115.187/webacs/api/v1/index4fcb.html?id=faq#persistent-connections">relevant FAQ item</A> for more details.</P><P></P><P>Second, if you have TACACS or some other non-local AAA provider configured on your Prime Infrastructure appliance, then timeouts between Prime and the AAA provider can result in 401 errors.&nbsp; In this case, try increasing the retry count and timeout configured in Prime Infrastructure&nbsp; To accomplish this, navigate to Administration &gt; Users &gt; User, Roles &amp; AAA.&nbsp; Then select either RADIUS, SSO, or TACACS, depending on which you use.&nbsp; Edit the server(s) and increase the retry, timeout, or both.</P><P></P><P>If neither of these cases applies to you, or you are still having problems after following the above, then please reach out and we can take a deeper look.</P></BODY></HTML> Mon, 22 Feb 2016 19:13:48 GMT Spencer Zier 2016-02-22T19:13:48Z Prime Infrastructure v2.2 REST API 401 Unauthorized error https://community.cisco.com/t5/controllers/prime-infrastructure-v2-2-rest-api-401-unauthorized-error/m-p/3472480#M1227 <HTML><HEAD></HEAD><BODY><P><SPAN style="color: #3d3d3d; font-family: arial; font-size: 12px;">Hi, Using Prime Infrastructure v2.2 REST API <SPAN style="color: #3d3d3d; font-family: arial; font-size: 12px;">ClientSessions. Every once in while I run into 401 Unauthorized error. Is there a downtime when this API service cannot be called?</SPAN></SPAN></P></BODY></HTML> Mon, 22 Feb 2016 17:31:11 GMT https://community.cisco.com/t5/controllers/prime-infrastructure-v2-2-rest-api-401-unauthorized-error/m-p/3472480#M1227 praveen.batchu1 2016-02-22T17:31:11Z Re: Prime Infrastructure v2.2 REST API 401 Unauthorized error https://community.cisco.com/t5/controllers/prime-infrastructure-v2-2-rest-api-401-unauthorized-error/m-p/3472481#M1228 <HTML><HEAD></HEAD><BODY><P>If you're seeing intermittent 401 errors, there are two probable causes.</P><P></P><P>First, check to make sure that you're not using persistent connections (which means sending the "Connection: keep-alive" header).&nbsp; Many clients will use persistent connections by default.&nbsp; You can either disable the persistent connection option in your client, or send the "Connection: close" header.&nbsp; See the <A href="https://developer.cisco.com/media/prime-infrastructure-api-reference-v3-0/192.168.115.187/webacs/api/v1/index4fcb.html?id=faq#persistent-connections">relevant FAQ item</A> for more details.</P><P></P><P>Second, if you have TACACS or some other non-local AAA provider configured on your Prime Infrastructure appliance, then timeouts between Prime and the AAA provider can result in 401 errors.&nbsp; In this case, try increasing the retry count and timeout configured in Prime Infrastructure&nbsp; To accomplish this, navigate to Administration &gt; Users &gt; User, Roles &amp; AAA.&nbsp; Then select either RADIUS, SSO, or TACACS, depending on which you use.&nbsp; Edit the server(s) and increase the retry, timeout, or both.</P><P></P><P>If neither of these cases applies to you, or you are still having problems after following the above, then please reach out and we can take a deeper look.</P></BODY></HTML> Mon, 22 Feb 2016 19:13:48 GMT https://community.cisco.com/t5/controllers/prime-infrastructure-v2-2-rest-api-401-unauthorized-error/m-p/3472481#M1228 Spencer Zier 2016-02-22T19:13:48Z