Configure Password Management on Web-Based Applications

the kron pam dynamic password controller manages many account types network devices, windows servers, unix systems, ad/ldap accounts, and many databases are managed without an agent structure, by using different protocols in the existing system while most web applications don't have an api for password changes, the dynamic password controller can manage web based applications without the need for an api why should you manage web based applications by kron pam? web based applications offer a range of business advantages over traditional desktop applications easier to develop more beneficial for users easy to install, maintain and keep secure easy to expand as the company grows managing web based applications in the management of web applications, the dynamic password controller is connected to the application via automation and the password changes are executed within the application settings the shared account password manager (sapm) configurations are defined in a “side” file format using javascript codes in the web app method sapm configuration property value change password template side file side file change password javascript codes check password template side file side file check password javascript codes how it works the user records a browser session of a password change for a web application, using browser extensions such as "selenium ide" the user replaces the password values in the "side" files with placeholders like "${old password}" "${new password}" the user exports these sessions in a "side" file format the user creates a new sapm configuration and uploads the "side" file when a password change trigger occurs, kron pam will execute the browser actions specified in the "side" file