1. Defining the Action in UI Design

• Open your project on the Kuika platform.
• Select the relevant screen in the UI Design module.
• Create a button (e.g., “Refresh Password”).

• Select the button and add the Authorization → User Password Force Change action from the + ADD ACTION menu according to the trigger event (Initial Actions, OnClick, etc.).

2. Configuring Action Parameters

• Username (String – required): The email address of the user whose password will be changed, as registered in the system.
• Password (String – required): The new password to be assigned to the user. It must meet security criteria (e.g., at least 8 characters, must contain uppercase/lowercase letters and special characters).

In a logistics application, truck drivers sometimes forget their passwords. Since the “ForgotPassword” process uses a custom provider, it does not come into play, and the user cannot reset their password. In this case, the administrator can define a new password for the driver using the User Password Force Change action.

Forcing the User Password to be Changed by the Admin

1. Open the UI Design module and drag and drop a Button element from the Elements panel on the left.
2. In the Properties panel, enter a phrase such as “Reset Password” in the button's Label section.
3. Select the relevant button and add the OnClick → Authorization → User Password Force Change action from the + ADD ACTION menu.

Configuring the User Password Force Change Action

• UserName: mary.watson@kuika.com (Name/email address of the user whose password will be changed. Can also be obtained dynamically from the form.)
• Password: NewPass#2025 (The new password to be set for the user. It must comply with security policies.)

How it works

With this configuration, when the administrator clicks the “Reset Password” button, the user's password in the system is changed immediately. The user can log in to the system with this new password that is sent to them.

• Dynamic Password Assignment: The password can be a random value generated by the system.
• Temporary Password Usage: A temporary password can be assigned to the user, who can then be directed to change their password via the auth flow (in scenarios without a custom provider).
• Form Integration: The password reset process can be performed by selecting the user from the administrator panel.

Technical Risks

• Password Security: Defined passwords must comply with security policies.
• Authorization Check: Since there is no authorization check within the action, this check must be performed during the design phase.
• User Notification: It is recommended to notify users whose passwords have been changed via email or notification.