RSA Version/Condition: 7.1.1
AFX requests that create and/or update Active Directory accounts are failing.
When viewing the request (Requests > Requests > [name of request]), AFX reports the following error on the request screen:
AFX reports this item failed with code [-1] and message: 'org.mule.api.transformer.TransformerMessagingException:
Unparseable date: "1567260660000" . Value of 'accountExipres' should be in 'MM/dd/yy HH:mm a' format. (java.lang.Exception).
Message payload is of type: String'. If available, another handler will be used to fulfill this item.
The connector log file, /home/oracle/AFX/esb/logs/esb.AFX-CONN-Active_DirectoryConnector.log, has the following errors:
Message : Unparseable date: "1567260660000" . Value of 'accountExipres' should be in 'MM/dd/yy HH:mm a' format. (java.lang.Exception)
Code : MULE_ERROR--2
--------------------------------------------------------------------------------
Exception stack is:
1. Unparseable date: "1567260660000" . Value of 'accountExipres' should be in 'MM/dd/yy HH:mm a' format. (java.lang.Exception)
org.mule.transport.ldapx.transformers.MessageToLdapEntry:53 (null)
2. Unparseable date: "1567260660000" . Value of 'accountExipres' should be in 'MM/dd/yy HH:mm a' format. (java.lang.Exception) (org.mule.api.transformer.TransformerException)
org.mule.transport.ldapx.transformers.MessageToLdapEntry:104 (http://www.mulesoft.org/docs/site/current3/apidocs/org/mule/api/transformer/TransformerException.html)
--------------------------------------------------------------------------------
Root Exception stack trace:
java.lang.Exception: Unparseable date: "1567260660000" . Value of 'accountExipres' should be in 'MM/dd/yy HH:mm a' format.
at org.mule.transport.ldapx.transformers.MessageToLdapEntry.getLdapAttributeForName(MessageToLdapEntry.java:53)
at org.mule.transport.ldapx.transformers.MessageToLdapEntry.transformMessage(MessageToLdapEntry.java:91)
at org.mule.transformer.AbstractMessageTransformer.transform(AbstractMessageTransformer.java:141)
+ 3 more (set debug level logging or '-Dmule.verbose.exceptions=true' for everything)
********************************************************************************
The issue occurs when the accountExpires value passed to the AFX Active Directory connector is not in the date format expected by AFX.
For the product version covered by this article, AFX expects the accountExpires value in the following format:
MM/dd/yy HH:mm
If the value is provided in a different format, AFX cannot parse the date, and the"Unparseable date" error occurs during the Create an Account or Update an Account operation.
Note: The required date format may differ in later product versions. Verify the expected format for the installed product version before changing the accountExpires mapping.
This article applies to the Create Account and Update Account operations described in this document.
Before applying the date-format mapping described below, verify that the error occurs during one of these operations and that your environment matches the versions covered by this article. An "Unparseable date" error can occur in other scenarios that have different causes and resolutions.
If the error occurs during Attribute Synchronization, refer to the appropriate Attribute Synchronization article, as the remediation described in this document may not apply.
Ensure that the accountExpires value mapped in the Active Directory connector definition uses the required date format for both the Create an Account and Update an Account connector capabilities.
For the product versions covered by this article, the required format is:
MM/dd/yy HH:mm
For example, for July 4, 2019, use:
07/04/19 00:00
In the RSA Identity Governance & Lifecycle user interface, go to AFX > Connectors > [name of connector] > Edit > Capabilities > [name of capability].
After updating the accountExpires mapping, retry the affected Create an Account or Update an Account operation and verify that:
- The operation completes successfully.
- The "Unparseable date" error no longer occurs.
- The accountExpires value is set to the expected date in Active Directory.
Related Articles
Active Directory AFX Connector Create Account capability fails when skip certificate validation in RSA Identity Governance… 420Number of Views Create Account fails if previous Create Account is pending in RSA Identity Governance & Lifecycle 115Number of Views Termination Date is not populated with the Account Expires date when running an Active Directory Identity Collector (IDC) … 118Number of Views Active Directory AFX 'Disable/Enable an Account' connector capabilities do not update added parameters in RSA Identity Gov… 254Number of Views Active Directory AFX Connector fails to create or modify accounts due to an 'LDAPException: Insufficient Access Rights' er… 273Number of Views
Trending Articles
RSA Authentication Manager 8.9 Patches and Hotfixes Readme AFX Server and Remote Collection Agents fail to start after updating Java to version 1.8u241 (1.8.0_241) / 1.7u251 (1.7.0_… Upgrade Internal Authentication Manager Certificates to SHA-256 RSA Authentication Manager 8.9 Setup and Configuration Guide Upgrading the Internal SecurID Authentication Manager 8.6 Certificates to SHA-256