AEM Custom Authentication Handler on Clustered Environment | Community
Skip to main content
A
AhmedHa
December 1, 2023
Solved

AEM Custom Authentication Handler on Clustered Environment

  • December 1, 2023
  • 3 replies
  • 1152 views

Hi,
I need support and suggestions,
I am currently using a custom authentication handler for oath openid, It works well on single author and publisher environment, Now we want to deploy our solution on production where there is a clustered environment i.e multiple dispatcher and publishers and authors and a load balancer before dispatcher. so how to it work in this clustered environment? How sessions will be managed as it is clustered enviornment ? what AEM suggested for this for Custom Authentication Handler.
The code for the authentication handler that I am utilizing is https://github.com/larsauffarth/oidc-authentication-handler/tree/main 

Looking forward for support.

Thanks

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 LarsAuffarth

Hi @ahmedha,

The referenced Authentication Handler requires sticky sessions to be in place, so that after successful OIDC authentication, the same publisher instance handles all subsequent requests. This is necessary, as the other publishers wouldn't have information on the initial successful OIDC authentication event.

As already mentioned above, and in my previous response on the blog post, user-synchronization will help in distributing any changes on the users across your publishers so that you have an eventually consistent state of your user base across your clustered environment.

Does that help?

3 replies

kautuk_sahni
Community Manager
kautuk_sahniCommunity Manager
Community Manager
December 4, 2023

@ahmedha Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.

Kautuk Sahni
L
Adobe Employee
LarsAuffarthAdobe EmployeeAccepted solution
Adobe Employee
December 5, 2023

Hi @ahmedha,

The referenced Authentication Handler requires sticky sessions to be in place, so that after successful OIDC authentication, the same publisher instance handles all subsequent requests. This is necessary, as the other publishers wouldn't have information on the initial successful OIDC authentication event.

As already mentioned above, and in my previous response on the blog post, user-synchronization will help in distributing any changes on the users across your publishers so that you have an eventually consistent state of your user base across your clustered environment.

Does that help?

    Terms & ConditionsAccessibility statement

    Loading footer...