# Upgrade assistant critical errors sollutions

**URL:** <https://discuss.elastic.co/t/upgrade-assistant-critical-errors-sollutions/182228>\
**Category:** Elasticsearch\
**Created:** [May 22, 2019, 12:45pm UTC](https://discuss.elastic.co/t/upgrade-assistant-critical-errors-sollutions/182228 "2019-05-22T12:45:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![MalfuncEddie](https://avatars.discourse-cdn.com/v4/letter/m/3da27b/32.png) [@MalfuncEddie](https://discuss.elastic.co/u/MalfuncEddie)\
**Post date:** [May 22, 2019, 12:45pm UTC](https://discuss.elastic.co/t/upgrade-assistant-critical-errors-sollutions/182228/1 "2019-05-22T12:45:43Z")

</div>

Hi,

I've successfully updated from 6.3.1 to 6.8 so that in the future I can upgrade to the 7.x release.  
I'm quite happy with the upgrade assistant since this tool shows me what I need to check.  
Only I quite confused what I need to do to resolve these issues

I've got 2 critical errors I need to resolve:

- Default TLS/SSL settings have been removed  
These are my current settings:

> ```
> xpack.security.enabled: true
> xpack.ssl.key: /etc/elasticsearch/censored.key
> xpack.ssl.certificate: /etc/elasticsearch/censored.cer
> xpack.ssl.certificate_authorities: /etc/elasticsearch/censored.pem
> xpack.security.transport.ssl.enabled : true
> 
> ```

Do I just add this?

> xpack.security.transport.ssl.enabled: true  
> xpack.security.transport.ssl.verification\_mode: certificate  
> xpack.security.transport.ssl.key: /etc/elasticsearch/censored.key  
> xpack.security.transport.ssl.certificate: /etc/elasticsearch/censored.cer  
> xpack.security.transport.ssl.certificate\_authorities: ["etc/elasticsearch/censored.pem"]
> 
> xpack.security.http.ssl.enabled: true  
> xpack.security.http.ssl.verification\_mode: certificate  
> xpack.security.http.ssl.key: /etc/elasticsearch/censored.key  
> xpack.security.http.ssl.certificate: /etc/elasticsearch/censored.cer  
> xpack.security.http.ssl.certificate\_authorities: ["etc/elasticsearch/censored.pem"]

Can these settings be done in a rolling restart of the nodes? or does the cluster need to be down?

- Security realm settings structure changed  
These are my current settings:

> xpack:  
> security:  
> authc:  
> realms:  
> native1:  
> order: 0  
> type: native  
> active\_directory:  
> bind\_dn: "censored"  
> # secure\_bind\_password: "use the keystore: /usr/share/elasticsearch/bin/elasticsearch-keystore add xpack.security.authc.realms.active\_directory.secure\_bind\_password"  
> domain\_name: "censored"  
> order: 1  
> type: "active\_directory"  
> url: "ldap://censored:389"  
> user\_search.base\_dn: "censored"

This needs to be changed to ?

> xpack:  
> security:  
> authc:  
> realms:  
> native.native1:  
> order: 0  
> active\_directory.active\_directory:  
> bind\_dn: "censored"  
> # secure\_bind\_password: "use the keystore: /usr/share/elasticsearch/bin/elasticsearch-keystore add xpack.security.authc.realms.active\_directory.secure\_bind\_password"  
> domain\_name: "censored"  
> order: 1  
> url: "ldap://censored:389"  
> user\_search.base\_dn: "censored"

---

<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:** [June 19, 2019, 12:45pm UTC](https://discuss.elastic.co/t/upgrade-assistant-critical-errors-sollutions/182228/2 "2019-06-19T12:45:56Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.