Renaming own user causes search to no longer work

book

Article ID: 222317

calendar_today

Updated On:

Products

CA Automic One Automation

Issue/Introduction

Renaming the user that is currently logged in causes a 401 Authorization header error (or in 12.3.4 to 12.3.6, a blank box shows) when searching for any object using AWI search

Steps to reproduce:
1) Log in as a non-LDAP user
2) Search for the user you are logged in as
3) Right-click the object and choose "Rename"
4) Rename the user
5) Attempt to search for the same or different object

Expected behavior:
Search results show

Actual behavior:
Search returns "Search Error: No Results"
In 12.3.3, there is a stack trace if you click on "Search Error: No Results" that says:
 java.util.concurrent.ExecutionException: com.uc4.ecc.backends.exceptions.AutomationEngineAPIException: [HTTP 401] (45229) Authorization header is missing.: No detail information available.
In 12.3.6 the error message is blank, but the error window still comes up - AWI log still shows:
 java.lang.RuntimeException: java.util.concurrent.ExecutionException: com.uc4.ecc.backends.exceptions.AutomationEngineAPIException: [HTTP 401] (45229) Authorization header is missing.: No detail information available.
This occurs until the user logs out and back in

Environment

Release : 12.3.0 to 12.3.6

Component : AUTOMATION ENGINE

Resolution

The two issues will be fixed in a future release:

There should not be a 401 Unauthorized Header error when renaming a user
The message box should always have a message in it

Both of these will be fixed in a future release.