Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

Vanity URL and CUG does not work together

Sam205505050
Level 6
Level 6

Is there any product limitation if I enable CUG and specify vanity url path of a page? 1. Create a page with CUG enable and specify vanity url path 2. Replicate this page in publish. 3. If I try to open using vanity url in publish server then I get 404 error.

  1. Is it a product bug?

I even tried to customize CUG implementation, so that if I open vanity url then Authentication should be on. And it is showing correctly. See the image attached. 

Now if I open vanity page(http://localhost:4503/happy3 is the vanity url and content node /content/test/mycomp/abc) then it ask me to enter username/password in default Geometrix login page even though I have SAML Authentication handler configured for this node /content/test/mycomp. After I logged-in through Geo metrixx login page and login-token cookie is created. Now again if I try to open http://localhost:4503/happy3 then I see ERR_TOO_MANY_REDIRECTS in browser.

  1. Why default Day CQ Login Selector Authentication Handler is coming where as I have SAML Authentication handler configured?
  2. What could be the reason of ERR_TOO_MANY_REDIRECTS even if I'm logged-in?

Thanks for your help

11 Replies
smacdonald2008
Level 10
Level 10

There is no such limitation in the AEM docs. What you may be encountering here is a bug. I recommend opening a support ticket so Support and Eng teams are aware of this issue. 

vamsikrishna199
Level 2
Level 2

Hi Scott,

I have implemented cug on one of the pages using customised login component. If i directly hit content path it is getting redirected to login page and it is working fine whereas if i directly hit vanity url, it is not navigating to the login page instead its showing me 404.

Kindly suggest me a solution.

Ankur_Khare
Community Advisor
Community Advisor

You need to allow that vanity path in your dispatcher as well ,as dispatcher doesn't recognize your vanity path and request doesn't go to cq thats why you are getting 404.

vamsikrishna199
Level 2
Level 2

Are you asking to provide redirection from long url to short url ?

Ankur_Khare
Community Advisor
Community Advisor

How are you accessing your vanity path?

If you are accessing vanity path from domain then you need to allow that vanity path in your dispatcher file.

I am not asking from long to short url.

vamsikrishna199
Level 2
Level 2

yeah but if i remove cug on that page, my vanity works but that is not expected

Ankur_Khare
Community Advisor
Community Advisor

I am not asking you to remove CUG, rather i am asking how are you accessing your page.

Are you trying to access your page from domain or directly publish instance.

vamsikrishna199
Level 2
Level 2

I am trying to access it directly through publish instance

Jörg_Hoh
Employee
Employee

Have you checked that the vanity URL property is actually present on publish?

vamsikrishna199
Level 2
Level 2

Yes the property is there in publisher instance. Currently my aem version is 6.3. Will it work fine in higher versions of aem ?

Jörg_Hoh
Employee
Employee

Can you check on publish the page at /system/console/slingauth. Under "Authentication Requirement Configuration" it should list a resources which should require authentication. Very likely only the "full paths" of the CUGs are listed, but not the vanity URLs. Can you please confirm?

regards,

Jörg