Best practice for placement of resetPasswordProperties node in case of authentication using AccountManagementService API | Community
Skip to main content
B
binoyp73053411
New Participant
December 14, 2021
Solved

Best practice for placement of resetPasswordProperties node in case of authentication using AccountManagementService API

  • December 14, 2021
  • 1 reply
  • 548 views

I could see the node being placed under /content in AEM in the reference article below

http://www.sgaemsolutions.com/2017/07/reset-password-using.html

Would it be best to maintain it below content ?

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 Pawan-Gupta

Hello,

 

I think its depend on your approach how you are planning to implement it. If, you are cross verifying via managing some validation that the person who is accessing this URL is same who requested for reset password then you are doing ok because you can easily stop those unwanted hit during validation (also, you can apply permission on this node hierarchy for access). But, if not then and want to protect your system from unwanted hits then captcha or moving this path configuration to Site context aware configuration (via wcm.io https://experienceleague.adobe.com/docs/experience-manager-core-components/using/developing/context-aware-configs.html?lang=en) will be better approach.

 

I hope, it helps you to make decision.

 

Thanks!!

1 reply

Pawan-Gupta
Pawan-GuptaAccepted solution
New Participant
December 14, 2021

Hello,

 

I think its depend on your approach how you are planning to implement it. If, you are cross verifying via managing some validation that the person who is accessing this URL is same who requested for reset password then you are doing ok because you can easily stop those unwanted hit during validation (also, you can apply permission on this node hierarchy for access). But, if not then and want to protect your system from unwanted hits then captcha or moving this path configuration to Site context aware configuration (via wcm.io https://experienceleague.adobe.com/docs/experience-manager-core-components/using/developing/context-aware-configs.html?lang=en) will be better approach.

 

I hope, it helps you to make decision.

 

Thanks!!

    Terms & ConditionsAccessibility statement

    Loading footer...