*ERROR* [qtp55964443-107234] org.apache.felix.http.jetty Exception while processing request to /system/console/fsclassloader getting org.apache.sling.api.auth.NoAuthenticationHandlerException | Community
Skip to main content
Shivanna
Shivanna
Level 2
May 4, 2021
Solved

*ERROR* [qtp55964443-107234] org.apache.felix.http.jetty Exception while processing request to /system/console/fsclassloader getting org.apache.sling.api.auth.NoAuthenticationHandlerException

  • May 4, 2021
  • 1 reply
  • 1682 views

Hi,

Greetings.

We are upgrading our platform to AEM6.5 and getting the below exception while accessing the /system/console/fsclassloader console on newly provisioned instances via below code. But same creds works fine manually. 

Does anybody has come across this issue already?

 

Jenkins logs : 

15:17:55 INFO [aem:recompile_jsps] uri : https://author1euwest1.dev65-aem.signify.adobecqms.net:443/system/console/fsclassloader?j_username=s...   &&

15:17:55 ERROR [aem:recompile_jsps] <aem65-li-dev-aem-cq-author> Request failed: 401 - Unauthorized.

 

AEM Instance log : 30.04.2021 08:44:26.197 *ERROR* [qtp55964443-107234] org.apache.felix.http.jetty Exception while processing request to /system/console/fsclassloader (org.apache.sling.api.auth.NoAuthenticationHandlerException)

 

Groovy Code :

def http = new HTTPBuilder("https://${httpconfig.host}:${httpconfig.port}")

http.ignoreSSLIssues()

http.client = HttpClients.createSystem()

http.request(method) { req ->

uri.path = path

uri.query = queryParam

response.success = { resp, jsonResponse ->

log.info "resp.statusLine--> ${resp.statusLine.statusCode}"

success = true

data = jsonResponse

}

response.failure = { resp ->

log.info "resp.statusLine--> ${resp.statusLine.statusCode}"

success = false

status = resp.statusLine

}

}

 

Thanks & Regards, Shiva

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 MarkusBullaAdobe

Hi @shivanna! 

Please try the following:

  • Have you double checked on the credentials used for that request?
  • Is your Jenkins server allowed to send these requests to the target instance (IP in allow list)?
  • Have you tried the same request from the Jenkins servers command line, e. g. with CURL?
  • Have you tried providing the credentials within your Groovy script (apply it to the HttpClient) instead of sending them as query parameters?
  • Have you tried providing the credentials in the "user:password@host:port/path" format instead of sending the as query parameters? 

 

Hope that helps!

1 reply

MarkusBullaAdobe
Adobe Employee
MarkusBullaAdobeAdobe EmployeeAccepted solution
Adobe Employee
May 4, 2021

Hi @shivanna! 

Please try the following:

  • Have you double checked on the credentials used for that request?
  • Is your Jenkins server allowed to send these requests to the target instance (IP in allow list)?
  • Have you tried the same request from the Jenkins servers command line, e. g. with CURL?
  • Have you tried providing the credentials within your Groovy script (apply it to the HttpClient) instead of sending them as query parameters?
  • Have you tried providing the credentials in the "user:password@host:port/path" format instead of sending the as query parameters? 

 

Hope that helps!

    Terms & ConditionsAccessibility statement

    Loading footer...