Looks like there are too many other requests coming in with that POST.
Can you try increasing the number of requests logged as described here?
http://www.albertoalmagro.com/en/how-to-increase-aem-recent-requests/
Maybe try setting it to 50 or 100 -- just remember to turn it back to 20
after you've grabbed the logs though.
I think @BrianKasingli hit this one on the head.If youre dead set on
automating this through custom code, two approaches to look at are:
First approach, Update Activate WF Model 1. Remove replication ACLs on
the content so the Activate Workflow Model is invoked when a user tries
to Publish2. Augment this Workflow Model to include a new Custom WF
Process Step3. This Custom WF Process Step would have available to it
the path of the Asset being activated, at which point you'd have to be
able to wri...
@Keerthi97 there is no magic bullet for this, since there are any number
of ways the HTTP POST endpoints maybe have been defined in AEM. In the
best case, all your HTTP POST endpoints are bound with well-known Sling
selectors -- so like, HTTP POST
/content/site-1/page.my-custom-submisssion.json, where
`my-custom-submission` is the identifying selector. If you have a set of
well-known selectors, you can allow POST whose URLs contain that
Selector or Path pattern .. some examples are here [1] If y...
The best practice to secure AEM Publish endpoints via Dispatcher is to:
1. First Deny EVERYTHING2. Then Allow only what you need to This is why
the first rule in the OOTB AEM Publish Dispatcher is "DENY *" [1] In
terms of identifying what URL end-points need to be ALLOWED in
Dispatcher for POST'ing depends on your application's design. Hopefully
custom POST end-points are bound to servlets registered to Servlets by
Resource Type and Selector/Extension, and the resource that has the
respective sl...
@santhoshm687661 Note that the UI says it shows a maximum of 20 requests
at a time. So here's what you need to do (and do these steps in rapid
succession).1. Tap the clear button on the Requests console (top
right)2. Trigger a POST to the end-point3. Refresh the Requests console
page4. Click on the POST to the end-point If this is a local instance,
you can also use AEM Chrome Plugin to capture this data on a per-request
basis (its actually immensely hands for development,
IMO)https://chrome.goog...
An asset's Tags and Keywords *ARE* Metadata. Both are data about the
asset. Generally, it's best to align to industry-standard
namespaces/properties. You'll see AEM even does this OOTB; instead of
inventing its own custom "dam:title" metadata property, it uses the
Dublin Core's "dc:title". Using industry-standard namespaces/properties
certainly makes your metadata more portable across applications that
might use your assets (these apps might be able to reason about industry
standard fields that ...
Are you attempting to block POST's on AEM Author or AEM Publish? If you
are trying to block POST's on AEM Author, don't 🙂 .. AEM uses POSTS and
especially those handled by the Sling Default POST servlet liberally.
Blocking anything that isn't a POST to a very specific URL is asking to
break AEM's OOTB functionalities. You should instead, use ACLs to
control what content/content trees an AEM Author can write to via the
POSTs (which will result in a 403, not a 200 if the user does not have
permis...
Sorry - I was talkinbg about the Request Progress Log in AEM available
via the OSGi console (http://localhost:4502/system/console/requests) ...
What you've posted is your Dispatcher log (which is good to know but
wont give us detailed info on how AEM is processing the request)
Figured yall might find this useful. I made a little Chrome Extension
for AEM as a Cloud Service development with Cloud Manager; It's not too
interesting but reduces some of the friction jumping between AEM CS and
Cloud Manager concerns. I tend to add/update/adjust it as I find
annoyances in my day-to-day that I can work around w/ this. Do note that
this currently only works on adobeaemcloud.com domains (since that's all
I use right now :)). Anyhow - this is not an Adobe-supported tool, but
feel...
@santhoshm687661can you please provide the Request Progress Log for this
request? This should help shed quite a bit of light of what's going on -
ex. does it stop processing at the CORS filter, or some other Filter, or
is it resolving to the incorrect servlet, etc.There is no known issue
with any version of AEM that turns non-204 responses to 204 responses. I
understand that this used to work pre-upgrade and doesn't now - but
you'll have to help w/ the investigation if you want to pinpoint and
r...
@Jai1122-1) if you are creating the JCR Session in your code (ie.
calling repository.login(..)) then you are responsible for closing that
JCR Session (preferably in a finally block). Your JCR Session used to
create a cq:User and/or its Token has nothing to do with the security
context the user gets when they login with the token. 2) Yes, again,
since your code is creating the resource resolver that calls your
RepoUtil, you need to also close that resourceResolver when you are
finished with it (i...
Yes, but only if you create that new JCR session/resourceResolver (aka
get a service user resourceresolver) you should close it as quickly as
possible, ie. when you're done with it. Don't leave them hanging around
for any longer than you need them. As Ideally you re-use the resource
resolver from with sling request, and since you dont make the resource
resolver from the sling request, you wouldnt close that (youd let Sling
close that one when its done processing the request)
Hi, Unfortunately, this looks like a regression. Please log an issue
with Adobe Support so AEM Engineering team can resolve. You could look
at injecting some CSS that resolves this issue in the interim. 1. Make a
new cq:ClientLibraryFolder under /apps to hold your temp fix. Assign
this ClientLibrary the following category:
cq.listview.coral.columns.personalization2. Add a new CSS file (ex.
fix.css) to this folder with the CSS rule:.coral-Table-wrapper.is-sorted
.coral-Table-row button[icon="drag...
100% don't initialize a resource resolver in your activate method. Keep
your ResourceResolvers/JCR Sessions short-lived as you can. Also,
rememeber resourceResolvers and JCR Sessions are NOT thread-safe. So if
you had a servlet being hit by 2 ppl at the same time, and they both
invoke the RepoUtil service using the same resourceResolver, bad things
will happen (like end up w/ lost data due to unresolvable state
conflicts) Here's what you should do (in order of generic preference),
1. Pass in the...
I think youll need to investigate more. Does this happen on your local
dev? Does this happen if you hit your custom servlet directly on AEM
(vs. going through dispatcher)? What is the Request Progress log for
this request (available in OSGi console)? Does your custom servlet have
any code that could return a 204 response?
I assume by "sonar properties" you mean setting blanket exclusions at
the POM level? It's typically unwise to blanket exclude entire
packages/classes from code quality checks. What you should do is:1.
Review violations reported by Cloud Manager, and fix the ones you can1.
There may be reported issues that aren't for whatever reason you do not
want to/cannot change, for these, it is better to explicitly suppress
that exact warning for just that method/class similar to [1]. This way
if you evolve ...
Do you have anything in your >/core/target/classes/OSGI-INF
folder? You should have a number of XML files, and a metatype folder
with more XMLs. Does this exist?
Another interesting solution could be the following: 1. For each
role/path combo - create a Hidden predicate on the Assets Search Form
1. Use the excludespaths QueryBuilder predicate to exclude a specific
path/path-pattern -- test this out as excludepaths seems like it might
be a little slower, you might be able to figure out how to do the
inverse using the paths predicate as well.1. Permission those hidden
predicates nodes in the JCR to be only read-able by members in the role
that shouldn't b...
This data is not persisted OOTB anywhere. If I were to attempt this I
would probably start by trying to inject Analytics code (by way of
Launch) into the ClientLibrary used for Search. This custom JS would
send the searched terms to Adobe Analytics (or whatever web analytics
system you have) which would hopefully provide you very easy reporting.
If the only place to store this data is in AEM Author, then I might
explore a Sling Filter that quickly accepts requests that match a
search, and also q...
Can you simply deny read permissions on the folder for the user group
that maps to this role?That will obviously result in these users not
being able to browse (or in general, see) these assets, but it sounds
like you might not want that anyhow?
You're supposed to be directly referencing anything in the
com.google.gson.internal package... that's why it's called "internal".
See the big warning on the GSON JavaDocs site for these internal
packages [1] that reads: Do NOT use any class in this package as they
are meant for internal use in Gson. Infact, this package is no longer
exported at all in later versions of GSON. The fix is to update your
code to depend on Gson's public API space. [1]
https://javadoc.io/doc/com.google.code.gson/gson/...
Adding a depdency in your pom is NOT the same as embedding the
dependency and deploying it as part of your package to AEM. You need to
do the latter. You can do this in a similar fashion as you embed your
Core OSGi bundle in your ui.apps content package.
After following the POM updates in the linked blog update, try the
following maven commands: $ mvn clean package -DskipTests$ mvn test IIRC
I would occasionally run into this issue if the OSGi SCR metadata XML
files weren't generated when the tests ran; doing the `mvn clean
package` would generate this for me and then allow my tests to run (you
could try dialing it back to `mvn clean compile` or other phases/goals)
You can overlay the menu node and add a rendition condition to it.
Overlay:
/libs/dam/gui/content/assets/jcr:content/actions/secondary/create/items/metadata
at
/apps/dam/gui/content/assets/jcr:content/actions/secondary/create/items/metadata
Add a rendition condition at:
/apps/dam/gui/content/assets/jcr:content/actions/secondary/create/items/metadata/granite:renderconditionYou
can do something like:sling:resourceType:
granite/ui/components/coral/foundation/renderconditions/privilegeprivileges:
jc...
Use this thread to ask any questions related to the Authenticating to
AEM as a Cloud Service from an external application on Experience
League. Experts are monitoring this thread to ensure your questions are
answered.
Try version 0.0.8+ of the repo modernizer plugin. The prior version
exhibited this symptom, and the way to work around it was to perform a
non-global install of
@adobe\aem-cs-source-migration-repository-modernizer in the same folder
in which you're running the aio plugin from. Ex.$ cd
project-to-modernize$ npm i
@adobe\aem-cs-source-migration-repository-modernizer But that said, that
was fixed in v0.0.8 so just upgrade to the latest version and you should
be set.
