AEM Error | Login Failure: all modules ignored | Community
Skip to main content
New Participant
November 24, 2016
Solved

AEM Error | Login Failure: all modules ignored

  • November 24, 2016
  • 9 replies
  • 12186 views

Hi All,

My below code is throwing exception, i am using AEM6.0. Followed all the instructions as suggested in http://adobeaemclub.com/access-to-resourceresolver-in-osgi-services-aem-6-1/

Map<String,Object> paramMap = new HashMap<String,Object>();
        paramMap.put(ResourceResolverFactory.SUBSERVICE, "readService");
        log.info("After the param");
        ResourceResolver rr = null;
        try{
            rr = resourceFactory.getServiceResourceResolver(paramMap);

        } catch(Exception ex) {

        }

And below is the exception 

org.apache.sling.api.resource.LoginException: Login Failure: all modules ignored
    at org.apache.sling.jcr.resource.internal.helper.jcr.JcrResourceProviderFactory.getLoginException(JcrResourceProviderFactory.java:394)
    at org.apache.sling.jcr.resource.internal.helper.jcr.JcrResourceProviderFactory.getResourceProviderInternal(JcrResourceProviderFactory.java:333)
    at org.apache.sling.jcr.resource.internal.helper.jcr.JcrResourceProviderFactory.getResourceProvider(JcrResourceProviderFactory.java:201)
    at org.apache.sling.resourceresolver.impl.tree.ResourceProviderFactoryHandler.login(ResourceProviderFactoryHandler.java:164)
    at org.apache.sling.resourceresolver.impl.tree.RootResourceProviderEntry.loginToRequiredFactories(RootResourceProviderEntry.java:95)
    at org.apache.sling.resourceresolver.impl.CommonResourceResolverFactoryImpl.getResourceResolverInternal(CommonResourceResolverFactoryImpl.java:154)
    at org.apache.sling.resourceresolver.impl.ResourceResolverFactoryImpl.getServiceResourceResolver(ResourceResolverFactoryImpl.java:91)
    at org.test.test.core.service.impl.ReadServiceImpl.listTitles(ReadServiceImpl.java:34)

 

Please advise to resolve the error.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by pradeepdubey82

It worked fine after creating system user and assigned all permission on /content folder.

9 replies

koushikd3750389
New Participant
January 19, 2018

But this is not the problem right ? All folder permission includes '/content' folder also.

New Participant
January 18, 2018

Full permission is needed only in /content folder

Not all folders.

koushikd3750389
New Participant
January 18, 2018

I have created a system user and give all the permission but still I am getting "Cannot derive user name for bundle com.xyz-aem.core [475] and sub service testService". It is a login exception. What is the wrong thing I am doing ? Any idea ?

pradeepdubey82AuthorAccepted solution
New Participant
December 13, 2017

It worked fine after creating system user and assigned all permission on /content folder.

New Participant
December 13, 2017

you should give Bundle Symbolic name. Check once in POM file and copy paste in OSGi User Mapper service configuration.

New Participant
November 25, 2016

Hi,

I tried normal user also. Still same error.

Please note my bundle full name is aem-sample-project-core-1.0.0-SNAPSHOT.jar and what i added in 'Apache Sling Service User Mapper Service' is                                                                 org.test.test.core.aem-sample-project-core:readService=testreaduser

And package name where my sling component exist is org.test.test.core.service.impl

What's wrong i am doing, please advise?

smacdonald2008
New Participant
November 24, 2016

Try a normal user on AEM 6

New Participant
November 24, 2016

I followed exactly same thing in video also tried like below in 'Apache Sling Service User Mapper Service'

org.test.test.core.aem-sample-project-core:readService=admin

Still getting same error. 

Since i am using AEM6.0 so system user option is not present i guess.

Correct me if i am wrong.

smacdonald2008
New Participant
November 24, 2016

You want to use the Sling Mapping service. See this HelpX video and corresponding article. The video shows you all steps in action: http://scottsdigitalcommunity.blogspot.ca/2014/12/querying-adobe-experience-manager-6.html?m=0.