Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vanity Url not working for Secured Pages without logging in #1449

Closed
3 tasks
ragv123 opened this issue Aug 3, 2018 · 1 comment
Closed
3 tasks

Vanity Url not working for Secured Pages without logging in #1449

ragv123 opened this issue Aug 3, 2018 · 1 comment

Comments

@ragv123
Copy link

ragv123 commented Aug 3, 2018

Required Information

  • AEM Version, including Service Packs, Cumulative Fix Packs, etc: _______6.3 SP2
  • ACS AEM Commons Version: _____3.13
  • Reproducible on Latest? yes

Expected Behavior

In our application, CUG are applied on all page except login page. When a page is accessed with actual url, user gets redirected to the login page and after logging in, page opens. Same should be the behavior with Vanity Url. If a user access the page with vanity url, if user is not logged in, it should be redirected to login page and if user is logged in, page should be open.

Actual Behavior

When a user try to access the page with vanity url, user gets 404 page instead of redirected to login page.

Steps to Reproduce

Created some pages, addd vanity url, and apply CUG on it. Install ACS Commons 3.13 version. Open ACS AEM COMMONS - Error page handler service in ConfigMgr and enable 'Vanity Dispatch Check'. Now access the page using vanity url. It will give 404 page.
We tried to debug it and found that, errorpagehandler's 404.jsp calls a service(vanityURLService) dispatch method. In this service, there is method isVanity which checks for the vanity path. But it uses current user resource resolver to resolve the path. Because, current user is not logged in and page is secured, resource resolver resolve method returns non-existing resource.
There are some logic performed which eventually returns false to jsp.
Now as response is false, jsp sets 404 status code and serve the 404 page to end user.

@stale
Copy link

stale bot commented Oct 13, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Oct 13, 2018
@stale stale bot closed this as completed Oct 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants