-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Password for shared PostgreSQL database will not be remembered #6869
Comments
My idea won't help you much: Somewhere in the preferences. I think, it is The JabRef team decided to remove any preference storing related tests, because tests should not change the developer's productive settings. Are the connection properties themselves remembered? I see following in the code - it could be that while switching from Java 8 to a higher version, the encryption algorithms might have get lost. - Do you see something in the log file? try {
setPassword(new Password(properties.getPassword().toCharArray(), properties.getUser()).encrypt());
} catch (GeneralSecurityException | UnsupportedEncodingException e) {
LOGGER.error("Could not store the password due to encryption problems.", e);
} |
Maybe because of the changes at #6853? |
This should be fixed in the latest development version. Could you please check the build from http://builds.jabref.org/master/. Thanks! Please remember to make a backup of your library before trying-out this version. |
This still was an issue in the latest release, should be finally fixed with #7364 |
JabRef version 5.2--2020-09-03--1283f9f on openSUSE Leap 15.1.
Steps to reproduce the behavior:
TimeOut
messages for SSLSocket on the console (see log files).Do you have an idea where the problem is?
Credentials input pane
When running (every 500 ms as defined in `PostgresSQLNotificationListener`)
socketTimeOut_SSL.log
The text was updated successfully, but these errors were encountered: