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

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

Avatar

Level 2

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

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

6.5
1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

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!

View solution in original post

1 Reply

Avatar

Correct answer by
Employee Advisor

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!