- Using Prime Infrastructure v2.2 REST API ClientSessions. Running into 401 Unauthorized error. Is there a downtime when this API service cannot be called.
If you're seeing intermittent 401 errors, there are two probable causes.
First, check to make sure that you're not using persistent connections (which means sending the "Connection: keep-alive" header). Many clients will use persistent connections by default. You can either disable the persistent connection option in your client, or send the "Connection: close" header. See the relevant FAQ item for more details.
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. In this case, try increasing the retry count and timeout configured in Prime Infrastructure To accomplish this, navigate to Administration > Users > User, Roles & AAA. Then select either RADIUS, SSO, or TACACS, depending on which you use. Edit the server(s) and increase the retry, timeout, or both.
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.
Please sign in to leave a comment.