---
title: Configuration Properties to Execute Commands After Changing Passwords
slug: kronpam-reference-guide-3-9-0/configuration-properties-to-execute-commands-after-changing-passwords
description: Learn how to change passwords effectively by executing specific commands and configurations. Discover the properties required for SSH and SMB strategies, such as post-command and execute.post.command.with.super.user. Find examples for both Windows and Lin
docTags: 
createdAt: 2022-07-29T12:25:51.000Z
---

Executing some commands after changing passwords might be necessary in some specific cases, such as killing active sessions that were started with the old password on the device. For these commands to be executed the following properties must be set in the configurations with SSH and SMB strategies:

| **post.command**                         | The commands to execute on the server after a successful password change.&#xD;<br />Multiple commands can be separated with \n characters. **&#xD;**                                                                                                                                                                                |
| ---------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **post.command.failure.pattern**         | If the pattern defined in this property is found in the “post-command” results, the command is accepted as "FAILED", and command execution is stopped. The remaining commands are not executed if the “post.command.stop.on.fail” property is set as “true”.                                                                        |
| **post.command.stop.on.fail**            | When the property value is set as “true”, if any failure occurs during post command execution, the remaining commands are not executed. The default value is “false”.                                                                                                                                                               |
| **execute.post.command.with.super.user** | If it is set as “true”, the super user credentials defined by the “super.username” and “super.password” properties are used to run the commands after the password change.&#xD;<br />The default value is “false”, meaning the Vault account username and password are used to run the commands after the password change.**&#xD;** |

:::hint{type="info"}
When using an SSH strategy, the last command in the **post.command** property must be a logout command.&#x20;
:::

**Windows Example**

| **post.command**                         | net stop Dnscache\nnet start Dnscache |
| ---------------------------------------- | ------------------------------------- |
| **post.command.failure.pattern**         | .\*invalid.\*                         |
| **post.command.stop.on.fail**            | false                                 |
| **execute.post.command.with.super.user** | true                                  |

**Linux Example**

| **post.command**                         | systemctl restart rsyslog\nlogout |
| ---------------------------------------- | --------------------------------- |
| **post.command.failure.pattern**         | .\*Failed.\*                      |
| **post.command.stop.on.fail**            | true                              |
| **execute.post.command.with.super.user** | true                              |