XssApi is null - 6.5 | Community
Skip to main content
S
sdouglasmcSonova
October 28, 2019
Solved

XssApi is null - 6.5

  • October 28, 2019
  • 4 replies
  • 6303 views

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?

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by Masoud_Rozati

    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.

    4 replies

    M
    Masoud_RozatiAccepted solution
    October 28, 2019

    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.

      S
      sdouglasmcSonovaAuthor
      October 28, 2019

      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.

      A
      aemdevn
      January 2, 2020

      Hi @sdouglasmcsonova 

      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
      Adobe Employee
      vijkumarAdobe Employee
      Adobe Employee
      May 5, 2020

      @aemdevn @masoud_rozati @sdouglasmcsonova 

      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);

        Linda_Jufferma1
        Linda_Jufferma1
        September 8, 2022

        I have

        import org.apache.felix.scr.annotations.Reference;
        import org.apache.sling.xss.XSSAPI;

        and

        @Reference
        private XSSAPI xssapi;

         

        but when I try to use the xssapi variable, it's null.

         

        Terms & ConditionsAccessibility statement

        Loading footer...