# Transport profiles with ES 7.5.0

**URL:** <https://discuss.elastic.co/t/transport-profiles-with-es-7-5-0/214407>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [January 9, 2020, 10:09am UTC](https://discuss.elastic.co/t/transport-profiles-with-es-7-5-0/214407 "2020-01-09T10:09:58Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![akappler](https://avatars.discourse-cdn.com/v4/letter/a/7c8e57/32.png) [@akappler](https://discuss.elastic.co/u/akappler)\
**Post date:** [January 9, 2020, 10:09am UTC](https://discuss.elastic.co/t/transport-profiles-with-es-7-5-0/214407/1 "2020-01-09T10:09:58Z")

</div>

Hi,

we configured ES 6.8.3 with a transport profile without mutual TLS authentication for use with a legacy client. Now we want to upgrade to ES 7.5.0, but the same configuration stopped working. Apparently no server certificate is generated, and the TLS handshake fails.

Here is the configuration:

```
  transport.profiles.client:
    port: 9500 
    xpack.security:
      type: client 
      ssl:
        client_authentication: none   

```

And here is the output of openssl when trying to connect to the transport profile:

```
openssl s_client -connect localhost:9500 Do 09 Jan 2020 11:09:18 CET
CONNECTED(00000003)
140007703086336:error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure:ssl/record/rec_layer_s3.c:1543:SSL alert number 40
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 7 bytes and written 293 bytes
Verification: OK
---
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 0 (ok)
---
```

---

<div class="post-metadata">

**Author:** ![akappler](https://avatars.discourse-cdn.com/v4/letter/a/7c8e57/32.png) [@akappler](https://discuss.elastic.co/u/akappler)\
**Post date:** [January 9, 2020, 11:12am UTC](https://discuss.elastic.co/t/transport-profiles-with-es-7-5-0/214407/2 "2020-01-09T11:12:45Z")

</div>

Update: I tried to configure the same certificates for the additional transport profile, and this configuration works.

```
transport.profiles.client:
    port: 9500 
    xpack.security:
      type: client 
      ssl:
        client_authentication: none 
        certificate: /usr/share/elasticsearch/config/node-transport-cert/transport.tls.crt 
        key: /usr/share/elasticsearch/config/node-transport-cert/transport.tls.key

```

Did something change in ES 7.x or in the operator, or is it intentional that no certificate is provided for additional transport profiles anymore?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [November 4, 2022, 7:40am UTC](https://discuss.elastic.co/t/transport-profiles-with-es-7-5-0/214407/3 "2022-11-04T07:40:01Z")

</div>