# ODK Aggregate configure PostgreSQL for SSL

**URL:** <https://forum.getodk.org/t/odk-aggregate-configure-postgresql-for-ssl/18532>\
**Category:** Support\
**Created:** [March 13, 2019, 9:43am UTC](https://forum.getodk.org/t/odk-aggregate-configure-postgresql-for-ssl/18532 "2019-03-13T09:43:06Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![ErikvdNeut](https://getodk.b-cdn.net/user_avatar/forum.getodk.org/erikvdneut/32/6227_2.png) [@ErikvdNeut](https://forum.getodk.org/u/ErikvdNeut)\
**Post date:** [March 15, 2019, 1:08pm UTC](https://forum.getodk.org/t/odk-aggregate-configure-postgresql-for-ssl/18532/2 "2019-03-15T13:08:34Z")

</div>

OK, fixed it myself 😀 Thanks to this topic: [JSON change-password request to /ssl/user-manage-passwords failed - #12 by Axlm](https://forum.getodk.org/t/json-change-password-request-to-ssl-user-manage-passwords-failed/18353/12)

I found this post from @ggalmazor :

> ```
> * Stop Tomcat
> * Create a backup of the whole directory where Aggregate is deployed
> * Unzip WEB-INF/lib/ODKAggregate-settings.jar into WEB-INF/classes
> * Delete WEB-INF/lib/ODKAggregate-settings.jar << this is important
> * Edit WEB-INF/classes/security.properties and set security.server.hostname with the IP address or hostname that the users will be using to access Aggregate
> * Start Tomcat
> 
> ```

There i found jdbc.properties in which the postgresql url is configured.

jdbc.url=jdbc:postgresql://sqlserver.mydomain.com/odk\_prod?autoDeserialize=true

According to the documentation @ [https://jdbc.postgresql.org/documentation/head/connect.html](https://jdbc.postgresql.org/documentation/head/connect.html) adding "?ssl=true" to the url should do the trick.

well, it did and ODKAggregate now connects to a postgresql database that enforces ssl connections.

---

_[View the full topic](https://forum.getodk.org/t/odk-aggregate-configure-postgresql-for-ssl/18532)._