Is your feature request related to a problem? Please describe.
Currently, when a user’s database password expires (Oracle, SQL Server, MySQL), PDFKeeper surfaces the provider error but does not offer an in‑application workflow to resolve it. Users must manually update their password through external tools or DBA intervention, interrupting their workflow and creating unnecessary friction.
Different database providers handle password expiration differently:
- Oracle requires OpenWithNewPassword
- SQL Server requires ALTER LOGIN
- MySQL supports password change during authentication using Old Password=
PDFKeeper needs a unified, consistent UX that abstracts these differences.
Describe the solution you'd like
Introduce a cross‑database password‑change abstraction and a clean UI workflow that activates automatically when a provider reports an expired password.
Is your feature request related to a problem? Please describe.
Currently, when a user’s database password expires (Oracle, SQL Server, MySQL), PDFKeeper surfaces the provider error but does not offer an in‑application workflow to resolve it. Users must manually update their password through external tools or DBA intervention, interrupting their workflow and creating unnecessary friction.
Different database providers handle password expiration differently:
PDFKeeper needs a unified, consistent UX that abstracts these differences.
Describe the solution you'd like
Introduce a cross‑database password‑change abstraction and a clean UI workflow that activates automatically when a provider reports an expired password.