KishCq5

How to capture Login events with SAML and SSO Authentication Handler - Adobe Experience Manager 08-01-2020

Hi All,We have an website running where AEM publishers are configured with SSO Authentication handler and SAML Authentication Handler. Intranet users are Authorized with SAML authentication and external users are authorized to application with SSO Authentication Handler with header name configured. Both the flows are working fine without issues.Now we want to capture the user login events and write to DB to enable one of the Reporting feature with Tableau.The question how can achieve this? Is th...

1.6K

Re: /var/audit dosent have page events updated in publisher - Adobe Experience Manager 05-12-2017

Hi Scot / kautuk,Thanks for the update. My real question is the audit logs not generated for pages in the publish instance but it does for the Assets. Is there any setting in Publisher to enable so that the nodes will be created under /var/audit for pages?Publisher: Author:

1.9K

/var/audit dosent have page events updated in publisher - Adobe Experience Manager 04-12-2017

Hi All,Under /var/events path in AEM 6.2 publish instance i am not seen any node getting created for the Page (com.day.cq.wcm.core.page) where as Author instance has all the events nodes updated.Is this default feature of the Publisher. How can i enable the page events to be added under /var/audit/com.day.cq.wcm.core.page in publisher?i want to query nodes under /var/audit/com.day.cq.wcm.core.page to get the information about page modificactions, deletions etc.Please help

2.1K

java.lang.Exception: Unable to get versions - After sidegrading using CRX2oak tool - Adobe Experience Manager 15-09-2017

Hi All,i have sidegraded content from Segmentstore to MongoDB using CRX2Oak tool. i wantedly ran the migration with parameter --copy-versions=false to reduce the copy size.Now the issue is lots of migrated nodes(Assests and Pages) has properties jcr:baseVersion ,jcr:versionHistory which has an unquie value which is version history.when i open the DAM UI in classic 6.2 instance there was an error for Assets which has the above mentioned property. I see an 500 error logged in the browser console.E...

1.9K

Re: LDAP users sync issue caused after AEM 6.2 in-place upgrade from AEM 6.1 - Adobe Experience Manager 19-06-2017

That worked. Adding 'rep:externalId' with the value of rep:principalName has solved the issue. Thanks a lot all

1.9K

Re: AEM 6.2 MongoDB(Enterprise V3.2.2) integration not working - Adobe Experience Manager 14-06-2017

if i use the vanila AEM 6.2 without Hotfx and SP1 it works fine. thanks for the support

14.2K

LDAP users sync issue caused after AEM 6.2 in-place upgrade from AEM 6.1 - Adobe Experience Manager 14-06-2017

Hi All,when we tried to perform an inplace upgrade from AEM 6.1 to 6.2 we are facing an issue with Authentication. we are using LDAP integration.There is a custom feature/ job running in our application daily which creates or update user details present in AEM home/users nodes. Adobe Experience Manager Help | Release Notes: AEM 6.2 Oak Cumulative Fix Pack in "Know issues" sections it was mentioned that If you are using Oak LDAP integration, then after applying the latest Oak hotfix, LDAP user sy...

2.8K

Re: AEM 6.2 MongoDB(Enterprise V3.2.2) integration not working - Adobe Experience Manager 13-06-2017

Hi Experts, can you please check and let me know if i am missing any steps in order to execute successful AEM with MongoDB integration.

14.2K

Re: AEM 6.2 MongoDB(Enterprise V3.2.2) integration not working - Adobe Experience Manager 13-06-2017

Hi edgarm,thanks for the reply. i tried adding the mongo.uri and db details as arguments while starting the AEM still the second instance is not starting properlyjava -jar aem6.2-author-p8001.jar -r crx3,crx3mongo -Doak.mongo.uri=mongodb://localhost:27017,localhost:27018 -Doak.mongo.db=aem_mongo_testcan you please let me know the steps you followed for the successful setup.

14.2K

Re: AEM 6.2 MongoDB(Enterprise V3.2.2) integration not working - Adobe Experience Manager 13-06-2017

Hi nschuter,Thanks for the steps i tried following the same1. started mongo instance in 270172. unpacked the jar3. updated the mongo configurations in start.bat of AEM4. started the AEM from command line start.batAEM is not coming up properly and i See error below in the logs. Only few bundles are in Active state.13.06.2017 12:35:15.389 *ERROR* [FelixStartLevel] ERROR: Bundle '36' Error stopping launchpad:resources/install/5/org.apache.felix.http.jetty-3.1.6-B002.jar (java.util.NoSuchElementExce...

14.2K

Likes from

User

Count

Learn

Documentation

Community

Support

Resources

Adobe account

Adobe