Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

How to configure cq login default page - OSGI root mapping configuration

Avatar

Level 4

Hello,

It is always forwarded to /welcome.html page automatically when I login (admin) to CQ author instance.

But I saw the root mapping of osgi configuration that is “/projects.html”.

I would like to know why the root mapping is invalidation. Did something block the login page?

 

Thanks for any help!

1 Accepted Solution

Avatar

Correct answer by
Employee

Thanks for the info - and just to let you know - I've tried on a straight-out-of-the-box installation, but I can't reproduce any of the issues.

View solution in original post

6 Replies

Avatar

Employee

Hello,

In AEM 6.0 the root mapping indicates the UI to be used as the default (i.e. touch-optimized or classic).

You can read more about this, and how to configure the setting, at:

The following page might help too:

If you have more questions, please let us know.

Avatar

Level 4

Thanks for your input and I have read the url pages.

But I mean that it always forwarded to classic UI no matter the ogsi root mapping is and even it is "/projects.html".

example: I put http://localhost:4502 on browser and it will jump to classic UI(see screenshot).

Do you know where can we configure the default UI except root mapping?

Avatar

Level 4

It seems like the URL issue and maybe it is url rewrite problem.

If url is http://localhost:4502 or http://localhost:4502/ and it will forward to classic UI.

If url is http://localhost:4502// and it will forward to touch-optimized UI.

Avatar

Employee

Can we ask you to confirm which version of AEM/CQ you are using?

Also, just to check - is this happening for every user account?

Thanks for the information

Avatar

Level 4

It is CQ5.6.1 version and happening for every one.

Avatar

Correct answer by
Employee

Thanks for the info - and just to let you know - I've tried on a straight-out-of-the-box installation, but I can't reproduce any of the issues.