Follow

How do I use the AuthAnvil Workflow editor?

Note: While our team can support the usage of the Workflow Editor and the Chrome Web recorder plugin, support for custom built Workflows is only provided via ProServices. If you would like to purchase Professional Services support key for help with your Workflow please contact your Account Manager via IAM.sales@kaseya.com.

Using the Workflow Editor

To set up the AuthAnvil Workflow Editor, first download it directly from your AuthAnvil Password Server. Go to the Admin > App Catalog page and under the Custom Apps tab there will be a download link for the AuthAnvil Workflow Editor. (Only Organization Administrators have access to this area)

You will then be prompted to install the software, and it will immediately launch the AuthAnvil Workflow Editor. There will be a Start Menu shortcut created under Scorpion Software > AuthAnvil Password Solutions for you to run the program next time.

Note You can only install the workflow Editor using Internet Explorer 10/11. Chrome no longer supports ClickOnce.


Prerequisites:

  • An existing installation of AuthAnvil Password Server v2.7
  • .NET Framework 4.5.2
  • Internet Explorer 10 or 11

 

Sequence Steps

Each Workflow is made up of a series of steps that simulate a web browser, like “Navigate to this URL” or “Fill in this form field”. These steps form the process of logging in or changing a password on a website. These are the available steps to make up those sequences.

Comment: Add text comments to provide information when reading through the Workflow. This step does not affect the execution of a Workflow

Delay: Wait for a certain number of seconds before continuing through the Workflow. Most steps require validation before they proceed so a delay may only be necessary when a special element takes longer to load than the page itself.

Add Log ItemNot currently used

Navigate to page: Navigate to a new page URL. Often used when redirecting to the “Change Password” page or when starting a Workflow. Note: All URLs must include the full prefix for http:// or https://

Set Form Field: Define an element inside an HTML form using the following parameters:

  1. Key – The identifier of a form field (i.e. <input name=”username“> or <input id=”username“>)
  2. Value – A label to identify this field when viewed in the synchronization page of AuthAnvil Password Server. Note: Must be unique from any other Value fields in this Sequence
  3. Input Type – The type of the HTML input element (i.e. <input type=”text” name=”username”>)
  4. Form Find by – Defines the form that this element will be linked with, either by Name or ID (i.e. <form id=”form1“> or <form name=”loginform“>)

Set Header ValueNot currently used

Set User Agent: Specify the user agent (browser) to simulate when connecting to the webpages. This can be used to provide a different visual display when logging in, or even to define a mobile browser to cause the target page to display differently

Submit Form: Define the context for submitting the HTML form using the following parameters:

  1. Actions – Form will be submitted to this Target URL using either the POST or GET method (i.e. <form id=”form1″ action=”submit.asp” method=”POST”>)
  2. Action Variable – A label to identify this field when viewed in the synchronization page of AuthAnvil Password Server. If defined, it will allow you to specify the form “Action” URL inside AuthAnvil Password Server. Note: Must be unique from any other labels in this Sequence
  3. Submit Value – An identifier representing the proper submit button for the form. This is to differentiate from other buttons or submit values on a page that may perform other actions like JavaScript functions
  4. Form Find by – Defines the form that will be submitted, collecting all of the form fields tied to this form by either Name or ID (i.e. <form id=”form1″> or <form name=”loginform”>)

Validate Page: Select an element on the page to use as validation that the Workflow has completed successfully. This will normally be a “Log Out” link verified by text, URL, or name, as a “Log Out” button will not display until you are successfully logged in.

Login and Change Password Activities

There are currently 2 sets of activities in a standard Workflow: Login and Change Password. The Login activities will emulate the process of logging in to a forms-based website. Change Password activities should start with a direct copy of the Logon activities, but will continue to perform the steps needed to change the user’s password.

Here is an example of a Login and Change Password activity set:

Login Activities

  1. Navigate to the login page
  2. Set the form fields including Username and Password
  3. Submit the login form
  4. Validate that the user has logged in

Change Password Activities

  1. Navigate to the login page
  2. Set the form fields including Username and Password
  3. Submit the login form
  4. Validate that the user has logged in
  5. Navigate to the Change Password page
  6. Set the form fields including Old and New Passwords
  7. Submit the form to update your password
  8. Validate that the password change succeeded

The default workflow of Navigate, Set, Submit, and Validate will not work with every forms-based website. Functions such as page redirects or additional form steps may require manual edits of a Workflow if it was created by the AuthAnvil Web Recorder

Validator

The Workflow Editor has a built in validation tool. This validator tool can be used to test the workflow before it is uploaded to the Password Server.

To Access the Workflow Validator tool simply open a workflow .SAMLX file and you will notice the following.

editor.PNG

 

Once you select Workflow Validator you will be able to test the login, validation & change steps as recorded.
editor2.PNG

This validator runs a headless Chrome browser and will screen shot each step of the workflow sequence.

 

Questions?

If you have any questions or need some help, we would be happy to assist. Open a case at help.scorpionsoft.com or send an email to support@scorpionsoft.com.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Powered by Zendesk