Ashutosh Sharma

@jesperpedersen, I have gone through the task and the corresponding files and I wish to continue this task, kindly assign me. ### Things to be fixed as per discussions ####...

> In pgagroal there should be a `GET_PASSWORD` management command. pgagroal should not "talk" to pgagroal-vault in any way. pgagroal should handle the changing of the frontend end user passwords....

> `pgagroal-vault.conf` will just have the configuration parameters needed for that process. I am thinking `pgagroal-vault.conf`, should be like this... ``` host pgagroal-host pgagroal-management-port # of pgagroal max_connections tls tls_cert_file...

I have one confusion here, regarding connecting **pgagroal-vault** with **pgagroal**, according to the above `.conf` file we are directing the `GET_PASSWORD` requests from **pgagroal-vault** (port 2500) to the `2345` port...

> Related to #407 and commit [5dcfb89](https://github.com/agroal/pgagroal/commit/5dcfb897d90b78c622a38855ae6ffd5cb2630d9f) on Rocky Linux 8 with gcc 11.4.1: > > ``` > [ 71%] Linking C shared library libpgagroal.so > [ 71%] Built target...

> @ashu3103 The bug fix should be a separate pull request Done!

Kindly first merge the bug-fix commit then I'll rebase this.

@jesperpedersen PTAL

> Aren't you missing the TLS properties in pgagroal-vault.conf for the `[main]` section ? While going through the code of `cli.c` and `security.c` I noticed that the TLS properties of...

> Ok, but at least we need documentation for that - so `doc/VAULT.md` and `doc/manual/user-12-vault.md` > I have added the requirements on how to enable SSL in `vault` in `doc/VAULT.md`...