This has been resolved with a call to technical support. The environment
in question was in-place upgraded from AEM 6.1 to AEM 6.4. Starting in
AEM 6.3 the Crypto Keys are stored in the file system by default. Prior,
the keys were stored in the repository. Because this system was in-place
upgraded, the keys stayed in the repository even though it is AEM 6.4.
Normally that is not a problem and the documentation indicates leaving
them in the repository is just fine. However there is at least one
Hi @CarmCon the below help document explains in detail:
Let us know if this helps.
Just sharing some info here: This is reported to the engineering team
via an internal ticket: CQ-4300140. This would happen when the list is
big and lazy loading happens. As a workaround, you can use /useradmin
Just a follow up. After working with technical support this is my
understanding of the issue... Turns out this is an issue when
configuring OSGi using the content-node method. When using content-node
and creating the configuration as a sling:OsgiConfig node with
properties there is no type of Integer. Typically Long will work in
place of integer, but the SSL Configuration Security Check code requires
the number to be an Integer for the SSL port property. As a work around
use the Adobe Web Consol...
It might help to better understand what you are after. Are you trying to
find out when the account was created? When they were granted permission
to a particular piece of content? The first time they edited content?
Something else? I am sure there are multiple ways to do it. One is to
look in CRXDE Lite (:/crx/de). Users are stored here:
/home/users. Find the user in question and then refer to jcr:created
property. This will tell you when the account was created. ...clint
The effects of a specific runmode are not really good covered in the AEM
documentation. Anyway, it's always advisable to define all
product-related runmodes (author, publish, crx3tar, ..., samplecontent,
nosamplecontent) before the first startup and then let them
configured.With your own runmodes the situation is of course different,
because you hopefully know the impact of them regarding your
application. (In case of the nosamplecontent runmode: as already said it
has an effect only during the ...