While Creating a Custom Authentication Handler in AEM- unable to register it under Sling Authentication | Community
Skip to main content
N
nikitagoyal
April 29, 2019
Solved

While Creating a Custom Authentication Handler in AEM- unable to register it under Sling Authentication

  • April 29, 2019
  • 3 replies
  • 2609 views

I am trying to implement a custom Authentication handler in AEM 6.4 by following the helpx document Adobe Experience Manager Help | Creating a Custom Authentication Handler for Adobe Experience Manager 6.4  

After following the document,

  • I have built and deployed the package successfully.
  • The Bundle is active.
  • The services are available and active in system/console/components.
  • I have whitelisted the bundle symbolic name as mentioned in https://forums.adobe.com/thread/2355506.

Still, I am unable to see the entry for the Custom Authentication Handler at http://localhost:4502/system/console/slingauth

Also, no errors as such noticed in the logs.

Has someone the same in AEM 6.4?  I there something I might be missing?

Can someone help me out with the right steps with implementation example.

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 nikitagoyal

Hi Shubham,

This looks like some issue with the project arch type.

it worked for me with the following :

  • AEM 6.4 and Maven arch type17
  • AEM 6.5 and Maven arch type 18

3 replies

Peter_Puzanovs
Community Advisor
Peter_PuzanovsCommunity Advisor
Community Advisor
April 29, 2019

Hi Nikita,

Should be OK, followed it recently,

Have you checked logs? Consider adding logger in activate method of the component Google 2F Authentication Handler to check that it actually activates.

The example is using OSGi annotations, is your project using them as well?

Regards,

Peter

shubhamg9400285
shubhamg9400285
Level 2
May 13, 2019

Hi Nikita,

same issue is happening with me, did you find any solution for this?

N
nikitagoyalAuthorAccepted solution
May 15, 2019

Hi Shubham,

This looks like some issue with the project arch type.

it worked for me with the following :

  • AEM 6.4 and Maven arch type17
  • AEM 6.5 and Maven arch type 18
Terms & ConditionsAccessibility statement

Loading footer...