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

SOLVED

XssApi is null - 6.5

sdouglasmc
Level 4
Level 4

I'm going through an upgrade from 6.3 to the latest 6.5.  In the code there are lines to get a reference to the XssApi:

import org.apache.sling.xss.XSSAPI;

this.xssAPI = this.resource.getResourceResolver().adaptTo(XSSAPI.class);

The problem is... xssAPI is "null".  I've tried referencing it as well with no luck:

@Reference

private XSSAPI xssAPI;

Has anyone else come across this issue?

1 Accepted Solution
Masoud_Rozati
Correct answer by
Level 2
Level 2

I had the same issue with adapting sling XSSAPI. If you use the (meanwhile deprecated) com.adobe.granite.xss.XSSAPI it can be adapted without any problem. You can also adapt it right from sling request.

View solution in original post

4 Replies
Masoud_Rozati
Correct answer by
Level 2
Level 2

I had the same issue with adapting sling XSSAPI. If you use the (meanwhile deprecated) com.adobe.granite.xss.XSSAPI it can be adapted without any problem. You can also adapt it right from sling request.

View solution in original post

sdouglasmc
Level 4
Level 4

Yeah, I tried that and it works just fine.  It's just really odd that it will actually work in 6.3 and not 6.5.  Crazy you have to "revert" for a newer version of AEM.

aemdevn
Level 1
Level 1

Hi @sdouglasmc 

Experienced the same issue after upgrading to 6.5...

I was using getRequest().adaptTo(org.apache.sling.xss.XSSAPI.class).getValidJSON("data", null) in 6.4.

It failed with an NPE  on getRequest().adaptTo(org.apache.sling.xss.XSSAPI.class);

Some one in https://stackoverflow.com/ gave the idea of using the service from the java class. 

so ended up coding this way:

getSlingScriptHelper().getService(org.apache.sling.xss.XSSAPI.class).getValidJSON(sdProp.toString(), null);

(Im using this from an Use java class)

Mentioning this here, in case this is useful for someones situation..

Thanks for asking the question here.

 

 

vijkumar
Level 3
Level 3

@aemdevn @Masoud_Rozati @sdouglasmc 

So this is what has changed and the reason it is failing now, in AEM 6.3 the 'com.adobe.granite.xssprotection' bundle wraps the 'org.apache.sling.xss' bundle and exposes its API with two versions:

  • 1.2.0
  • 2.0.1

In AEM 6.5 the decision by our R&D team was taken to update the 'org.apache.sling.xss' API version to 2.0.1 only. Since now the 'org.apache.sling.xss' bundle allows configuring from where the AntiSamy policy is read, this essentially removes the need for the bundle to be wrapped by the Granite API. Thus now in AEM 6.5 'com.adobe.granite.xssprotection' bundle does not wraps the 'org.apache.sling.xss' bundle. The 'org.apache.sling.xss' bundle is now provided as a individual bundle in AEM 6.5.


As an affect of this change, the classes or scripts referring XSSAPI should be adapted in order to get their 'org.apache.sling.xss.XSSAPI' reference through OSGi dependency injection. Something like [1] should be used in place of [2].


If this is not possible, then the deprecated com.adobe.granite.xss.XSSAPI should be used.

[1]

import org.apache.felix.scr.annotations.Reference;
...

@Reference
private XSSAPI xssAPI;

[2]

XSSAPI xssAPI = request.adaptTo(XSSAPI.class);

AEM6.3AEM6.3AEM6.5AEM6.5AEM6.5AEM6.5