portal proxy status stays disconnected after upgrading gateway to 11.1.2
Article ID: 408618
Updated On:
Products
Issue/Introduction
After upgrading gateway from version 11.1.0 to 11.1.2 the proxy status in API Portal stays disconnected and we are unable to deploy any api's to gateway .
Reverting back gateway to the old release does resolve the problem .
On the initial start of the gateway there is a error in the ssg log which looks like
{"package":"com.l7tech.external.assertions.portaldeployer.server.client.MessageProcessor","level":"INFO","log":{"message":"PUT callback request to https://portal-ssg.portaldomain:443/tenant/deployments/internal/proxies/UUID/integration-details?isDeploymentCallback\u003dtrue\u0026gatewayNodeId\u003 failed. Request body: {\"status\":\"DEPLOYED\",\"message\":\"[{\\\"status\\\":\\\"DEPLOYED\\\",\\\"message\\\":\\\"{\\\\\\\n\\\\\\\"bundleVersion\\\\\\\": \\\\\\\"UTC.20241231.1200.00\\\\\\\",\\\\\\\n\\\\\\\"otkVersion\\\\\\\": \\\\\\\"4.6.2-7680\\\\\\\",\\\\\\\n\\\\\\\"gatewayVersion\\\\\\\": \\\\\\\"11.1.2\\\\\\\",\\\\\\\n\\\\\\\"ssgNodeName\\\\\\\":\\\\\\\"GatewayName\\\\\\\",\\\\\\\n\\\\\\\"clusterName\\\\\\\": \\\\\\\"domainname\\\\\\\",\\\\\\\n\\\\\\\"buildInfo\\\\\\\": \\\\\\\"Layer7 API Gateway 11.1.2 build 20324, built 20250321234025 by root at a811605b0b3a\\\\\\\",\\\\\\\n\\\\\\\"invocationTimeInUtc\\\\\\\": 20250521121750200\\\\\\\n}\\\",\\\"targetLocation\\\":\\\"https://localhost:8443/portalman/1/integration-details\\\"}]\"}, response code: 500, response body: { \"error\":
On the portal apim log there is a
[time]-[INFO ]-[274]-[]-[com.l7tech.server.policy.assertion.ServerSslAssertion]-4113: No Client Certificate was present in the request.
Resolution
The portal deployer is unable to connect to the gateway correctly because the gateway certificate is not reaching the portal , the used Nginx server in front of the portal does not support java 17 which is causing issue's with the ssl passthrough which only work sometimes
The workaround on the gateway could be to disable the new feature for java 17 ssl handshake and set the java setting jdk.tls.server.enableSessionTicketExtension = false or upgrade the nginx server to a version which support Java 17
see also
Feedback
