@RitendraS11 This seems to be a custom implementation of AEM DataLayer
As per , the problem is specific to user access, and I hope you
may have cross-checked these articles.In the case at hand, dispatcher
logs would help identify why the form submission is stuck on the
dispatcher layer. You may want to skim the mandatory AEM Forms
configurations (if applicable) for dispatchers .  -
https://githubhelp.com/PerficientDigital/AEM-DataLayer/issues/2  -
@StrawHatM23 The steps provided in the introduction article are short
and crisp, so may seem confusing. You can refer to the other help docs
on the left panel under "AEM Forms and Adobe Campaign Standard." Also,
another article elaborates the steps to integrate AEM with ACS, so
you can follow that in parallel for any confusion.Needless to say, as
@workflowuser requested, please share your inputs so that we can improve
this article.  -
@Vindiesel Which component are you referring to? Could you
elaborate?There is an option to add text as a placeholder for most
components, so you can check that.More information -
Hope this helps!
@coldwarsoldier Thanks for getting back!Yes, at times, we have noticed
that you have to log in to the CRX console first before you could use
any of the other Felix/AEM consoles.More context: Ideally, when you try
to access any URL, it will redirect to
, but the abovementioned problem
may arise when you have incorrectly updated the Sling authentication
service previously.Now that you're able to login, you can check
whether:1. "Apace Sling Authentication Service" config under /configMgr
has the pr...
@Monica_Allamneni Thanks for sharing the code snippet.As per , when
you create an instance of HtmlEmail, set its properties and then invoke
the send() method, the object will internally invoke the following
methods:buildMimeMessage()sendMimeMessage()It is ok to invoke
sendMimeMessage() multiple times, such as a send-with-retry scenario.
The problem is that buildMimeMessage() can only be invoked once. When
you rely on the send() base class method, you get the exception found by
the original po...
@StrawHatM23 This is a server-side exception during submission; that's
why you see the message “Encountered an internal error while submitting
the form” on the browser side. Could you share the detailed error logs
to identify the root cause?
@coldwarsoldierBased on an internal discussion, AEM Forms SPNEGO SSO
supports AES-256, and this switch shouldn't cause any issues.Based on
, I can see that type 18 is aes256-cts-hmac-sha1-96 so this
encryption needs to be updated in the Kerberos config file otherwise
these configurations will remain the same.In case of any issues,
enable the Debug logs on server, set the parameters
-Djcsi.kerberos.debug=true, -Didm.spnego.debug=true and share the logs.
@Nick_Hilton Forms practice test is listed here but the actual
practice test is not available -
https://adobe.gmetrix.net/Tests/ChooseTest.aspx @MorisMonk  -