Details
-
Type:
Bug
-
Status: Resolved
-
Priority:
High
-
Resolution: Fixed
-
Affects Version/s: 5.0.4
-
Fix Version/s: 5.0.5
-
Labels:None
-
Environment:Canada, others
-
Severity:Critical - Defect that prevent from carrying out a feature, use case could be accomplished with the help of an operator, memory leak
-
Frequency:Frequent - Regularly used feature or bug that happens often with common parameters
-
Account:Support N3 (SUPPORTN3)
-
Program Increment:None
-
Targeted team:Default
Description
We discovered it on the Canadian platform but this is surely impacting every of them that includes the secured channel feature. When using TLS without enabling mutual authentication, an NPE shows up in the logs (see attached).
Sometimes, we did not figure out yet when and how, the message is not captured by the proxy but most of the time it is done well. In fact we don't know exactly which is the impact of this exception.
It is caused by a null certificate being sent by the proxy when being a client (then communicating with a server). This makes sense with the checkbox unchecked but it should not raise an exception. The possibility of this certificate being null must be handled well in the code.
The error is linked to the TlsEventListener.java class. sslEngine.getSession().getLocalPrincipal() needs to be evaluated and hanled when null is returned.
Sometimes, we did not figure out yet when and how, the message is not captured by the proxy but most of the time it is done well. In fact we don't know exactly which is the impact of this exception.
It is caused by a null certificate being sent by the proxy when being a client (then communicating with a server). This makes sense with the checkbox unchecked but it should not raise an exception. The possibility of this certificate being null must be handled well in the code.
The error is linked to the TlsEventListener.java class. sslEngine.getSession().getLocalPrincipal() needs to be evaluated and hanled when null is returned.
