How to fix the Adobe LiveCycle Client SDK Configuration to prevent it from locking the admin account? | Community
Skip to main content
M
msgtowers
Level 3
October 20, 2017

How to fix the Adobe LiveCycle Client SDK Configuration to prevent it from locking the admin account?

  • October 20, 2017
  • 1 reply
  • 10243 views

I installed AEM 6.3 Forms on JEE yesterday, and this morning the admin account was locked.  After looking at the log, I found multiple admin account logging attempts.  I found a fix the fix bellow, but I cannot access the site listed.  Either I get this error

JBWEB000309: type JBWEB000067: Status report

JBWEB000068: message

JBWEB000069: description JBWEB000123: Access to the specified resource has been forbidden.

or

You have reached this page because cookies might not be enabled on your browser. Please enable the cookies and then re access the LiveCycle application.

I made sure that the browser accepts all cookies.

Changing administrator password on AEM Forms JEE | The LiveCycle & AEM Forms survival kit

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

U
Adobe Employee
user7587541Adobe Employee
Adobe Employee
October 20, 2017

It's likely that you haven't whitelisted the machine you're trying to access the server from.  If you have access to the server launch a browser on the server and you should be able to get access to the url.  Your other option is to go to adminui and whitelist the machine you want to access or NOT RECOMMEDED remove all the elements then any machine can gain access.

M
msgtowersAuthor
Level 3
October 20, 2017

I tried to access the Adobe LiveCycle Client SDK Configuration link from both the server running AEM 6.3 Forms, and from my workstation with the same results.  Can you explain "whitelist"?  Thank you.

U
Adobe Employee
user7587541Adobe Employee
Adobe Employee
October 20, 2017

Can you connect to localhost:port/adminui?  If so refer to Adobe Experience Manager Help | Preventing CSRF attacks

Terms & ConditionsAccessibility statement

Loading footer...