javax.jcr.AccessDeniedException: Access denied. (500) | Adobe Higher Education
Skip to main content
nickt39971962
nickt39971962
Level 2
August 22, 2019
Beantwortet

javax.jcr.AccessDeniedException: Access denied. (500)

  • August 22, 2019
  • 11 Antworten
  • 6232 Ansichten

All of our deploys have started failing with the following error. Even trying to deploy packages that have previously been installed results in the same error. Could anyone tell me how I can start investigating a problem like this? I don't see anything useful in the logs.

This problem is happening on our stage publishers and all of our production instances but our stage author is working fine. I know that is a clue but I'm not sure where to look.

[ERROR] Request failed: javax.jcr.AccessDeniedException: Access denied. (500)

[INFO] Looks like the package was not installed, checking the list...

[INFO] package not installed, re-uploading it...

[ERROR] Request failed: javax.jcr.AccessDeniedException: Access denied. (500)

    Dieses Thema wurde für Antworten geschlossen.
    Beste Antwort von vish.dhaliwal

    Hello,

    What is the procedure of the package deployment? Since there is an Access Denied Exception, check if it works with admin user.

    Check if the same user can install packages through the package manager.

    Regards,

    Vishu

    11 Antworten

    Vorherige Antworten anzeigen
    Gaurav-Behl
    Gaurav-Behl
    Level 10
    August 23, 2019

    Couple of questions:

    1) Does the issue happens with  '-Pauto-install-bundle' or '-Pauto-install-package' or both profiles? -- based on your statement 'We are deploying use maven content plugin with bundle auto install.'?

    2) If the issue happens with 'auto-install-bundle'  - can you verify that the '/apps/.../install' folders (http://localhost:4502/apps/mycompany/parent/install​) exists when you use that profile? Assuming there are no permission issues on /apps/.../install since you use admin credentials.

    Adding Filter tag to content-package-maven-plugin fails probably because it expects either <includes> or <embeddeds>

    check Managing Packages Using Maven

    On a side note, <usePut>true</usePut> is deprecated

     

    Allgemeine NutzungsbedingungenAccessibility statement

    Loading footer...