@ranjitha29 "Request for Activation" workflow model is automatically
triggered if the user clicking activate doesn't have replication
privileges under the path. See here as
well:https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-6-1-request-for-activation-process/qaq-p/293565/comment-id/59768
Hi @gclarke2,Our sales team should have a lot of information for you.
Please contact them via the info on this
page:https://www.adobe.com/request-consultation/experience-cloud.htmlJust
tell them what you need and they should be able to provide
it.Thanks,Andrew
The only ways to avoid the issue:1. Create a script to create the user
nodes in AEM ahead of time2. Enable sticky sessions on the load balancer
so the user is always sent to the same AEM instance.
As @Jörg_Hoh said, please file a support ticket. The saml response XML
gets stored in encrypted form under the user node. That xml isn't
complying with the xmil structure that the createLogoutRequest method
expects. So we might need to do some debugging there.
SurendraKonatha.Once you get access then please let me know which ones
you need, I will make sure they are published in the software
distribution site for you and others to download. Thanks,Andrew
I'm not sure, but it sounds like based on your description you are
trying to serve a static HTML file via AEM? Here is another forum post
on the same
thing:https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/hosting-static-html-in-the-jcr/qaq-p/223359
@Albin_Issacif you look at the stack trace the the HashMap throwing the
exception is from Apache Jackrabbit Oak code at
org.apache.jackrabbit.oak.security.authorization.permission.PermissionEntryProviderImpl.loadEntries(PermissionEntryProviderImpl.java:163)
[org.apache.jackrabbit.oak-core:1.8.7] I filed an issue for this, if
possible, please update with more details on the
issue:https://issues.apache.org/jira/browse/OAK-9117
What version of AEM is this? What version of oak-core bundle do you see
in /system/console/bundles? I would like to contact Adobe Engineering
team for this issue. I suspect there is a product issue here. See the
issue I filed here: https://issues.apache.org/jira/browse/OAK-9117
Here are the Microsoft APIs you would need to
use:https://github.com/OfficeDev/Office-365-SDK-for-Javahttps://docs.microsoft.com/en-us/previous-versions/office/office-365-api/
There is no need to store stuff on AEM directly, per my understanding.
The likely reason the workflow would get aborted would be due to the
payload being published/replicated, see this article:
https://helpx.adobe.com/experience-manager/kb/workflow-is-getting-aborted-without-any-error-or-exception.html
Since there is no way to define which handler on the same path to
trigger for authentication you would have to do some customization. You
could implement a custom servlet /bin/auth and configure the
authentication handlers under subpaths of the servlet - for example
/bin/auth/saml. When the user accesses the AEM site via method requiring
SAML then set a cookie to remember their original entry point and
redirect to that servlet with a querystring saying which type of
authentication. For
Example:/...
Here is the correct doc for
6.5:https://docs.adobe.com/content/help/en/experience-manager-65/administering/security/saml-2-0-authenticationhandler.html
Sorry for the confusion with the 6.3 doc, I will notify our docs team.
AEM's SAML handler doesn't parse out the CN from the DN. However, you
can just use the DN in AEM and it doesn't have to be visible to users.
You can create the groups in AEM with the DN as the id, for example,
"CN=APP-CRM-BUILD-PROFILE-CSR,OU=Resources,OU=_Groups,DC=lan,DC=xxxx,DC=org",
then just give the group a friendly name in the group title. Why the
need for it to be the CN? DN isn't a bad thing, it avoids naming
conflicts.
You must configure the IDP to send the value you want. This isn't
handled by AEM. In the AEM SAML Handler OSGi configuration, you would
just set the "Group Membership" property with the name of the SAML
attribute containing the list of the user's memberships (containing the
group CNs instead of DNs). Based on my findings, I suspect you are using
OpenAM IDP from Forgerock, is that correct? If so, I guess you would
need to implement a custom attribute
mapper:https://backstage.forgerock.com/knowled...
1. See the Single Page Application (SPA) feature set for AEM, here is
the React
tutorial:https://helpx.adobe.com/experience-manager/kt/sites/using/getting-started-spa-wknd-tutorial-develop/react/chapter-1.html
If that is too tightly integrated then see the headless CMS features of
AEM:https://docs.adobe.com/content/help/en/experience-manager-learn/getting-started-with-aem-headless/overview.htmlhttps://www.adobe.com/experience-cloud/topics/headless-cms.htmlhttps://www.hcltech.com/blogs/understand...
Hi @sarakellyn the official channel for pricing is
here:https://www.adobe.com/products/request-consultation/marketing-cloud.htmlPlease
fill out the form or call the number there and somebody would assist
you.
I wrote a small app recently that does this so I could debug a product
issue with content-sync. You can download it
here:https://documentcloud.adobe.com/link/track?uri=urn%3Aaaid%3Ascds%3AUS%3A52ae18bd-a1c4-48e6-b63f-25e31019bc6b
The app is under /apps/test/test.jspYou run it by going to
/apps/test.html
Your maven pom.xml file for bundle IA_Wrapper_Services.core has the
dependency for org.sling.apache.event set with the wrong version
(mismatch to 6.5 version). Please match your dependency version config
for org.apache.sling.event in the pom.xml to match the bundle in
/system/console/bundles.
If ResourceOnly flushes don't solve this then you can look into
implementing a custom invalidation handler
script:https://docs.adobe.com/content/help/en/experience-manager-dispatcher/using/configuring/dispatcher-configuration.html#using-custom-invalidation-scriptshttps://arborydigital.com/blog/2019/12/05/aem-dispatcher-custom-invalidation-scripts/
Depending on the AEM version, you might also be hitting a product issue
where response headers are reset on serving of asset files. To address
that, you can apply the latest service pack - test locally to confirm.
@jkpanera for now, until we have such documentation, you could search
the json in this tool for the
versions:https://helpx.adobe.com/experience-manager/kb/tools/bundle-version-checker.html
This might be caused by a known issue in Apache Sling
https://issues.apache.org/jira/browse/SLING-8469I would suggest to
update to AEM 6.5 service pack 3 (6.5.3) as it includes the fix.
You cannot block admin from creating, modifying or deleting nodes. User
"admin" bypasses all system permission checks. It would be best to just
not share the admin user password with your team. As @huangb8 said,
anonymous user cannot create nodes.
Please contact our AEM support team to debug this, this is an
interesting problem I haven't heard of before. I have never seen a case
where offers from other pages get mapped to another page. So it would be
good to find the root cause.
I agree with @Jörg_Hoh, the concept of having different builds removing
/ adding configs could be prone to issues and isn't the recommended
approach. Leveraging runmodes is good for environment specific stuff and
if you have site / path specific functionality then maybe you could
drive that via Sling Context Aware
configs:https://sling.apache.org/documentation/bundles/context-aware-configuration/context-aware-configuration.html
Otherwise, in general, adding / removing OSGi components per build w...
If runmodes aren't preferrable as this is build specific and not
environment specific then you could dynamically set the OSGi
configurations via your
code:http://www.nateyolles.com/blog/2015/10/updating-osgi-configurations-in-aem-and-slingYou
might consider to have some separate projects in your maven builds that
build different package for deploy per build that have different OSGi
configs. There are many ways to achieve what you want, it is just to
decide how to implement it.
https://maven.apac...
One way to do what you want is to make it so an OSGi configuration needs
to be available for the component to be enabled (this is called
ConfigurationPolicy.REQUIRE on the OSGi Component). See here, for
example:http://www.computepatterns.com/43/osgi-component-in-aem-that-is-active-only-in-specific-run-mode-say-publish/
Then using this, you can leverage runmodes like
/apps/myapp/config.qaauthor, /apps/myapp/config.qapublish. Or you can
enable them by removing the config of one component and enabl...
Instead of disabling basic auth on publish, just don't include
Authorization header in the /clientheaders config of the dispatcher
configuration. That effectively prevents basic auth from the outside
world.
I'm going to assume you mean rep:policy nodes. If that is the case then
this article covers
it:https://helpx.adobe.com/experience-manager/kb/migrate-users-groups-ACLs.html
What is the difference between OSGI Services and OSGI Components tabs
within the OSGI Apache Felix Console? An OSGi Component can implement
one or more OSGi services. It sounds like in your case, you had the OSGi
Component class defined as its own service. Components can have
configurations associated with them.See the OSGi Declarative Services
Specification for the formal definition (in the generated bundle jar an
XML file defines the
configuration):https://osgi.org/specification/osgi.cmpn/7.0....
