# TLS Configuration in Aerospike Connect Spark Connector

**URL:** <https://discuss.aerospike.com/t/tls-configuration-in-aerospike-connect-spark-connector/10840>\
**Category:** Spark\
**Tags:** spark\
**Created:** [February 19, 2024, 5:01pm UTC](https://discuss.aerospike.com/t/tls-configuration-in-aerospike-connect-spark-connector/10840 "2024-02-19T17:01:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![amanjain08](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/amanjain08/32/2209_2.png) [@amanjain08](https://discuss.aerospike.com/u/amanjain08)\
**Post date:** [February 19, 2024, 5:01pm UTC](https://discuss.aerospike.com/t/tls-configuration-in-aerospike-connect-spark-connector/10840/1 "2024-02-19T17:01:12Z")

</div>

I am using version 2.8.1 of the Aerospike Spark connector to read data from the Aerospike server. Although our Aerospike server does not require client certificate validation and only needs the `tlsName` parameter to establish a secure connection, when I set `aerospike.tls.enabletls: true` and `aerospike.tls.tlsname: <tlsName>` in the Aerospike Spark connector, I receive an error with reason code `java.lang.IllegalArgumentException`. The error message indicates that the mandatory TLS truststore properties (`aerospike.tls.truststore-store-file` and `aerospike.tls.truststore-store-password-file`) is missing.

However, in our Java application (not Spark), we are able to successfully read data from the Aerospike server by only providing the `tlsName` parameter without any additional truststore properties.

AS Client Version: 6.1.2

---

<div class="post-metadata">

**Author:** ![Rahul\_Kumar1](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/rahul_kumar1/32/2207_2.png) [@Rahul\_Kumar1](https://discuss.aerospike.com/u/Rahul_Kumar1)\
**Post date:** [February 22, 2024, 4:14am UTC](https://discuss.aerospike.com/t/tls-configuration-in-aerospike-connect-spark-connector/10840/2 "2024-02-22T04:14:00Z")

</div>

1. The 2.8.1 version of the connector is no longer supported. It is recommended to upgrade to a newer version, which offers significantly more functionalities and improved performance.
2. Could you please double-check that there were no certificates present in your TLS setup? I’m puzzled as to how there could be TLS communication without certificates. Additionally, could you verify if the server log confirms TLS communication in your setup?