Paul Dekker

+1

wrong post, excuse me

I recognize your issue. My solution is working with a service account. That acocunt has very low rights in Passwordstate, is only used for scheduled reports. This is absolutely not a nice way bacause I first have to change my own account: disable SSO. After changing the report(s) I have to enable SSO on my account again.

We prefer installing of application on a AKS Kubernetes (Docker) cluster in stead of a dedicated server. Please make Passwordstate available for Kubernetes.

When using the ScrablePad PIN, a user can change the PIN code into a bad code like 0000 or 1111. Passwordstate does not check the bad passwordlist and it is not possible to enforce a strong(er) PIN code. Request: I would like a new parameters in the Systems settings, tab Authentication options: - The ScramblePad PIN code must contain at least x-number of different digits

When calculating a password in the password generator in the browser extention, the generator does not check to the "bad password list". Result: you might receive (and use) a password that does not fit to the checks of PWstate when you add the password to a passwordlist. Result: error when storing the record in PWstate, and a need to change the password in the application. My wish is that the password generator will be integrated to PWstate, recognizes bad passwords and those words not uses in the generated password.