Current Behavior: The DUO Update User action (duo.update_user) does not expose alias1–alias8 fields as parameters. The only alternative is the generic Admin API Action (duo.admin_api_general), but its params field appears to send data as query parameters rather than form-encoded POST body data. The DUO Admin API's Modify User endpoint (POST /admin/v1/users/{user_id}) requires parameters to be sent as form POST body data to apply updates.

As a result, when using the Admin API Action with method: POST and params: {"alias4": "tempadmin-user"}, DUO returns stat: OK but silently ignores the alias parameter — the alias is never set.

Expected Behavior (either would resolve the issue):

Preferred: Add alias1–alias8 as optional parameters on the existing Update User action, since it already handles DUO API authentication and form encoding correctly.

Alternative: Update the Admin API Action to send params as form-encoded POST body data when the method is POST, rather than as URL query parameters.

Use Case: We are building a Just-in-Time Admin Access workflow that needs to dynamically add a temporary admin alias to a user's DUO account, then remove it after the access window expires.