Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

Repository Exception in Lead Creation Workflow OakAccess0000: Access denied

Avatar

Level 2

Hi All,

I have successfully configured salesforce integration in AEM per this article.

However, I am getting the following error when exporting AEM user as a lead (as mentioned in Integrating with Salesforce ​ section of the above link):

03.08.2018 17:07:43.310 *ERROR* [JobHandler: /var/workflow/instances/server0/2018-08-03/salesforce-com-export_14:/home/users/we-retail/-ovva86cmKknBL-dJNLw/profile] com.adobe.cq.mcm.salesforce.SalesforceExportProcess Repository Exception in Lead Creation Workflow OakAccess0000: Access denied

03.08.2018 17:07:43.310 *ERROR* [JobHandler: /var/workflow/instances/server0/2018-08-03/salesforce-com-export_14:/home/users/we-retail/-ovva86cmKknBL-dJNLw/profile] com.day.cq.workflow.compatibility.CQWorkflowProcessRunner Process execution resulted in an error: Repository Exception in Lead Creation Workflow OakAccess0000: Access denied

com.day.cq.workflow.WorkflowException: Repository Exception in Lead Creation Workflow OakAccess0000: Access denied

at com.adobe.cq.mcm.salesforce.SalesforceExportProcess.execute(SalesforceExportProcess.java:278) [com.day.cq.mcm.cq-mcm-salesforce:1.5.4]

at com.day.cq.workflow.compatibility.CQWorkflowProcessRunner.execute(CQWorkflowProcessRunner.java:93) [com.day.cq.workflow.cq-workflow-impl:6.2.12]

at com.adobe.granite.workflow.core.job.HandlerBase.executeProcess(HandlerBase.java:194) [com.adobe.granite.workflow.core:2.0.168]

at com.adobe.granite.workflow.core.job.JobHandler.process(JobHandler.java:261) [com.adobe.granite.workflow.core:2.0.168]

at org.apache.sling.event.impl.jobs.JobConsumerManager$JobConsumerWrapper.process(JobConsumerManager.java:502) [org.apache.sling.event:4.2.10]

at org.apache.sling.event.impl.jobs.queues.JobQueueImpl.startJob(JobQueueImpl.java:293) [org.apache.sling.event:4.2.10]

at org.apache.sling.event.impl.jobs.queues.JobQueueImpl.access$100(JobQueueImpl.java:60) [org.apache.sling.event:4.2.10]

at org.apache.sling.event.impl.jobs.queues.JobQueueImpl$1.run(JobQueueImpl.java:229) [org.apache.sling.event:4.2.10]

at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

at java.lang.Thread.run(Unknown Source)

I am executing the Salesforce.com Export workflow as an Admin user.

Any inputs on what could be wrong here ?

Environment: AEM 6.4

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

Please check with Adobe support if an ootb feature is not working properly. The need to change ACLs of service-users is definitely something you should discuss with support.

Jörg

View solution in original post

5 Replies

Avatar

Level 10

I have checked with internal people to see if this is a know issue.

Avatar

Employee

Based on the error, it looks like Salesforce service user in AEM does not have sufficient ACL to users’ profiles. Saleforce metadata is expected to be saved into profile and it doesn’t have RW permissions.

Avatar

Former Community Member

Hi Experts,

Is this issue resolved? I am facing same error? what was the resolution please?

Thanks

Avatar

Level 2

I was able to successfully execute the Salesforce.com Export workflow once I assigned the user "workflow-process-service"  permission to Read, Modify,Create, Delete, etc.. to the /home/users/* path

A new property called leadID is now added for the exported user and I can see following success message in AEM error.log:

/var/workflow/instances/server0/2018-08-17/salesforce-com-export_22:/home/users/Y/VUg3H4jC4oZ11-XzjVF8/profile] com.adobe.cq.mcm.salesforce.SalesforceExportProcess New Salesforce Lead Created with Success (id: 00Q1H0000141OMqUAM)

Avatar

Correct answer by
Employee Advisor

Please check with Adobe support if an ootb feature is not working properly. The need to change ACLs of service-users is definitely something you should discuss with support.

Jörg