Who Me Too'd this topic

I have a user where their TACACS accounts is unable to login to the Cisco Prime server after they run our Java client that connects to Cisco Prime using the HTTP REST API calls.

1. The user showed us that he could login with the TACACS account to the Cisco Prime gui via the browser.
2. Runs the Java Client that is using a local Cisco Prime account to execute the HTTP REST API calls.
3. Tries to login with the TACACS account to the Cisco Prime gui via the browser after the Java client completes.  The message after attempting the login is: "invalid username or password please try again"
4. In order to login to Cisco Prime, the user, logins with his local Cisco Prime account, non TACACS account.
5. Navigates to the Administration / Users / User,Roles & AAA screen.
   1. Changes the AAA mode from TACACS+ to Local then clicks on the save button
   2. Changes the AAA mode from Local to TACACS+ then clicks on the save button
6. Now when the user tries to login with his TACACS+ account, he is able to login

Below are the APIs used by our Java Client.  We may make several ConfigVersions and extractUnsanitizedFile  calls since our Java client is pulling the device configurations from Cisco Prime.

/webacs/api/v1/data/Devices

/webacs/api/v1/op/devices/exportDevices

/webacs/api/v1/data/ConfigVersions

/webacs/api/v1/op/configArchiveService/extractUnsanitizedFile

Any ideas on what could cause this behavior?  The version of Cisco Prime is 3.1.

Thanks,

Eddy