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
BedrockMission!

Learn More

View all

Sign in to view all badges

AEM ADMIN Pages are not working

Avatar

Avatar
Validate 1
Level 2
ashwiniv5325199
Level 2

Like

1 like

Total Posts

22 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 1
View profile

Avatar
Validate 1
Level 2
ashwiniv5325199
Level 2

Like

1 like

Total Posts

22 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 1
View profile
ashwiniv5325199
Level 2

07-12-2018

Hi Team,

                I upgraded one of my project repo from SCR Annotation to DS OSGI Annotation. The project's functionality is working as expected in both the annotations.But when the project which is in DS annotation is installed into the AEM instance, SITEADMIN, DAMADMIN, USERADMIN, MISCADMIN are not working fine. Please can anyone suggest the solution for this issue.

Logs are as below:

*INFO* [0:0:0:0:0:0:0:1 [1544183000975] GET /siteadmin HTTP/1.1] org.apache.sling.xss.impl.HtmlToHtmlContentContext AntiSamy warning: The link tag contained an attribute that we could not process. The type attribute had a value of "image/vnd.microsoft.icon". This value could not be accepted for security reasons. We have chosen to remove the entire link tag in order to continue processing the input.

*INFO* [0:0:0:0:0:0:0:1 [1544183066525] GET /damadmin HTTP/1.1] org.apache.sling.xss.impl.HtmlToHtmlContentContext AntiSamy warning: The link tag contained an attribute that we could not process. The type attribute had a value of "image/vnd.microsoft.icon". This value could not be accepted for security reasons. We have chosen to remove the entire link tag in order to continue processing the input.

*INFO* [0:0:0:0:0:0:0:1 [1544183105759] GET /useradmin HTTP/1.1] org.apache.sling.xss.impl.HtmlToHtmlContentContext AntiSamy warning: The link tag contained an attribute that we could not process. The type attribute had a value of "image/vnd.microsoft.icon". This value could not be accepted for security reasons. We have chosen to remove the entire link tag in order to continue processing the input.

*INFO* [0:0:0:0:0:0:0:1 [1544183193170] GET /miscadmin HTTP/1.1] org.apache.sling.xss.impl.HtmlToHtmlContentContext AntiSamy warning: The link tag contained an attribute that we could not process. The href attribute had a value of "/libs/wcm/core/content/misc.ico". This value could not be accepted for security reasons. We have chosen to remove the entire link tag in order to continue processing the input.

Thanks for your response in advance.

Regards,

Ashwini

Replies

Avatar

Avatar
Coach
MVP
Arun_Patidar
MVP

Likes

1,356 likes

Total Posts

3,227 posts

Correct Reply

917 solutions
Top badges earned
Coach
Contributor 2
Ignite 10
Give Back 700
Boost 1000
View profile

Avatar
Coach
MVP
Arun_Patidar
MVP

Likes

1,356 likes

Total Posts

3,227 posts

Correct Reply

917 solutions
Top badges earned
Coach
Contributor 2
Ignite 10
Give Back 700
Boost 1000
View profile
Arun_Patidar
MVP

07-12-2018

Hi,

Its look like antisamy configuration issue. Could you check configurations

Antisamy configuration locations

Avatar

Avatar
Validate 1
Level 2
ashwiniv5325199
Level 2

Like

1 like

Total Posts

22 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 1
View profile

Avatar
Validate 1
Level 2
ashwiniv5325199
Level 2

Like

1 like

Total Posts

22 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 1
View profile
ashwiniv5325199
Level 2

10-12-2018

Thanks for your response.

But this solution did not resolve my issue.Antisamy configuration is present in crxde.

In my case, some other factor is responsible for the above problem.

Avatar

Avatar
Validate 25
Level 10
smacdonald2008
Level 10

Likes

1,408 likes

Total Posts

12,671 posts

Correct Reply

2,278 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Give back 900
Give back 600
View profile

Avatar
Validate 25
Level 10
smacdonald2008
Level 10

Likes

1,408 likes

Total Posts

12,671 posts

Correct Reply

2,278 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Give back 900
Give back 600
View profile
smacdonald2008
Level 10

10-12-2018

This can be some sort of upgrade bug. This should not happen. I recommend that you open a support ticket so the customer support team can investigate this. You may need a hotfix only they can provide. 

Avatar

Avatar
Validate 1
Level 2
ashwiniv5325199
Level 2

Like

1 like

Total Posts

22 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 1
View profile

Avatar
Validate 1
Level 2
ashwiniv5325199
Level 2

Like

1 like

Total Posts

22 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 1
View profile
ashwiniv5325199
Level 2

11-12-2018

Thanks for your response.

But other repos with DS annotation is working perfectly fine. Only problem with my repo which I recently changed from SCR to DS annotation