Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions en/collaborative-work/sqldatabase/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,8 @@

To use this feature you have to connect to a remote database. To do so you have to open **File** in the menu bar and then click the **Connect to shared database** item. The **Connect to shared database** dialog will open and you will have to fill in the shared's database connection settings. Then, you have to fill out the remaining fields with the according information. If you like you can save your password by clicking the **Remember password?** checkbox.

Every database you connect to is remembered. The **Saved connections** list at the top of the dialog lets you pick a previous connection to fill in the fields again, and **Remove** deletes the selected one together with its stored password. Connecting to a database that is already in the list updates its entry, so the list holds each database once; connecting with changed server, database or user details adds a new entry.

Check warning on line 11 in en/collaborative-work/sqldatabase/README.md

View workflow job for this annotation

GitHub Actions / vale-lint

[vale] reported by reviewdog 🐶 [write-good.Passive] 'is remembered' may be passive voice. Use active voice if you can. Raw Output: {"message": "[write-good.Passive] 'is remembered' may be passive voice. Use active voice if you can.", "location": {"path": "en/collaborative-work/sqldatabase/README.md", "range": {"start": {"line": 11, "column": 31}}}, "severity": "WARNING"}

### SSL configuration

Since version 5.0 JabRef supports secure SSL connection to the database. For PostgreSQL make sure the server supports SSL and you have correctly setup the [certificates](https://www.postgresql.org/docs/current/static/ssl-tcp.html). Then [convert the client certificates](https://jdbc.postgresql.org/documentation/ssl/#configuring-the-client) into a java readable format and import them into a (custom) keystore. For MySQL the procedure is similar. [Setting up MySQL with SSL](https://dev.mysql.com/doc/refman/8.0/en/using-encrypted-connections.html) and converting the certificates for the java keystore. However, it has only been tested with PostgreSQL. Once the certificates are imported into the keystore, specify the path to the keystore file in the connection dialog and the password for accessing the keystore.
Expand Down
Loading