> For the complete documentation index, see [llms.txt](https://docs.sealights.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealights.io/knowledgebase/setup-and-configuration/troubleshooting-faq/java/ssl-certificate-errors/ssl-connectivity-java-7-pre-u131.md).

# SSL Connectivity: Java 7 (Pre-u131)

### Problem <a href="#problem" id="problem"></a>

When running with the SeaLights Java agent, depending on the proxy and security setting, an SSL connection can be encountered when using java 7 with a version lower that 131.

### Cause <a href="#cause" id="cause"></a>

This is due to TLS 1.2 not being added by default till java 7 version 131 (See <https://www.oracle.com/technetwork/java/javase/7u131-relnotes-3338543.html>)

### Solution <a href="#solution" id="solution"></a>

The solution is to upgrade java to version 131 or later which will automatically support TL1.2, if you are using an older version of Java 7 then you can add the following JVM param: `-Dhttps.protocols=TLSv1.2`.

> **Add TLS v1.1 and v1.2 to the client list of default-enabled protocols**\
> TLSv1.2 and TLSv1.1 are now enabled by default on the TLS client end-points.\
> This is similar behavior to what already happens in JDK 8 releases.

In some cases there may be a cipher suite mismatch between the Java 7 environment and the TLS 1.2 supporting peer.\
Additional ciphers can be added using an extra JVM param e.g. "`-Dhttps.cipherSuites=TLS_RSA_WITH_AES_128_CBC_SHA256`" (comma separated list if adding multiple ciphers)

### Related articles <a href="#related-articles" id="related-articles"></a>

* [Running Tests](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/go-agent/go-agent-v1/running-tests.md) (Go)
* [Setting up a windows service](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/.net-core-agent/capturing-coverage-from-the-application/ms-windows-specific-configurations/setting-up-a-windows-service.md) (.Net Core)
* [Setting up IIS Listener](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/.net-core-agent/capturing-coverage-from-the-application/ms-windows-specific-configurations/setting-up-iis-listener.md) (.Net Core)
* [Cloud Foundry Integration](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/python-agent/capturing-coverage-from-runtime-application/cloud-foundry-integration.md) (Python)
* [Pivotal Cloud Foundry (PCF) Support](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/java-agent/pivotal-cloud-foundry-pcf-support.md) (Java)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sealights.io/knowledgebase/setup-and-configuration/troubleshooting-faq/java/ssl-certificate-errors/ssl-connectivity-java-7-pre-u131.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.