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
BedrockMission!

Learn More

View all

Sign in to view all badges

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

Avatar

Avatar
Establish
Level 1
Shivanna
Level 1

Like

1 like

Total Posts

16 posts

Correct Reply

0 solutions
Top badges earned
Establish
Boost 1
Validate 1
Give Back
View profile

Avatar
Establish
Level 1
Shivanna
Level 1

Like

1 like

Total Posts

16 posts

Correct Reply

0 solutions
Top badges earned
Establish
Boost 1
Validate 1
Give Back
View profile
Shivanna
Level 1

04-05-2021

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

Accepted Solutions (0)

Answers (2)

Answers (2)

Avatar

Avatar
Establish
Level 1
Shivanna
Level 1

Like

1 like

Total Posts

16 posts

Correct Reply

0 solutions
Top badges earned
Establish
Boost 1
Validate 1
Give Back
View profile

Avatar
Establish
Level 1
Shivanna
Level 1

Like

1 like

Total Posts

16 posts

Correct Reply

0 solutions
Top badges earned
Establish
Boost 1
Validate 1
Give Back
View profile
Shivanna
Level 1

04-05-2021

@asutosh_jena : Thanks for your response.

Yes. Connectivity looks fine from Jenkins server to AEM server. Validated using telnet from Jenkins server.

Avatar

Avatar
Affirm 100
Level 10
asutosh_jena
Level 10

Likes

373 likes

Total Posts

480 posts

Correct Reply

133 solutions
Top badges earned
Affirm 100
Ignite 1
Establish
Give Back 50
Give Back 5
View profile

Avatar
Affirm 100
Level 10
asutosh_jena
Level 10

Likes

373 likes

Total Posts

480 posts

Correct Reply

133 solutions
Top badges earned
Affirm 100
Ignite 1
Establish
Give Back 50
Give Back 5
View profile
asutosh_jena
Level 10

04-05-2021

Hi @Shivanna 

 

I see you are trying to access this newly provisioned instance from Jenkins.

Please check if you have the Jenkins host whitelisted to access the AEM instance.

 

Thanks!