Issue
If you are accessing any LiveCycle services and have problems getting a response, you may notice the following warning in the server logs:
WARN [com.adobe.idp.common.errors.exception.IDPLoggedException] (Thread-21) UserM:GENERIC_WARNING: [Thread Hashcode: 1859008299] com.adobe.idp.common.errors.exception.IDPLoggedException| [AuthenticationManagerBean] errorCode:12817 errorCodeHEX:0x3211 message:The user <user> is marked as Obsolete
If you enable DEBUG level logging you will see the following DEBUG information in the log:
=========== Authentication failure detail report ================== Scheme Type : Username/Password UserId : user Current Thread : ajp-0.0.0.0-11148-2 Following users were identified as per received authentication data. Details are (UserId, domain, oid) - user, DefaultDom, 7C5E5622-96A9-102F-AE67-00000XXXXXXX Following are the response details from various authProviders. 1 - com.adobe.idp.um.provider.authentication.LDAPAuthProviderImpl - Authentication Failed : Exception stacktraces are avialable at TRACE level Messages collected for this AuthProvider are provided below - LDAP authentication failed for user [user] in Domain [corp.domain] - Unprocessed Continuation Reference(s) 2 - com.adobe.idp.um.provider.authentication.LocalAuthProviderImpl - Authentication Failed : Exception stacktraces are avialable at TRACE level Messages collected for this AuthProvider are provided below - The user user is marked as Obsolete - No local user found with UserId [user] in Domain [DefaultDOM]
These warnings in the log may also be accompanied by an Error 500 if you are attempting to call the LC services through a browser/web application.
Reason
This issue can occur when you are attempting to access the services with a user account that has been marked obsolete in the LiveCycle database. This can occur if you have deleted this specific user from LDAP or from the local domain in LiveCycle.
If you have written applications depending on this user account then you will encounter the problem outlined above when running/calling those applications.
Solution
You could either re-create the user in your LDAP or local domain, or you can create a new user and then change your application to reference this new user rather than the obsolete user account.
reference: (183305926)