This documentation supports the 20.08 version of Remedy Action Request System, which is available only to BMC Helix subscribers (SaaS).
To view an earlier version, select the version from the Product version menu.

Mapping XML data types using Username Token authentication

The WS-Security WS-Security Username Token 1.0 standard allows you to specify whether you send the password in digest or plain text format. Digest format is a hash, and the consuming web service must know the password to authenticate the password.

For documents describing the WS-Security Username Token 1.0 standard, see


For a web service that requires the Username Token, the selected WSDL might not indicate that a Username Token is required. In that case, the designer must know whether the web service requires the Username Token and create the workflow accordingly.

With the Username Token method, you can perform any of the following tasks or a combination of any of them:

  • Enter a static value for the user name and password
  • Map fields to the appropriate attributes
  • Use the run time BMC Remedy AR System user name and password

With this method, Developer Studio automatically sets the XML attributes arUsername: true and arPassword: true, but this is not reflected in the Mapping Info column. For this method, the Mapping Info column defines whether to send the password in digest or plain text format.

Input mapping for the Username Token authentication method

(Click the image to expand it.)

To map fields or assign static values for the user name and password elements, follow the procedures in Mapping XML data types using AR Authentication.

To assign digest or plain text format to the password element

  1. Click in the Mapping Info cell for the Password element.
  2. Click the drop-down menu that appears, and then select Digest or Text.
Was this page helpful? Yes No Submitting... Thank you