Scan automations that use Email action for Gmail with Basic authentication

You can use the Automation 360 Bot Scanner to scan automations that are using Gmail with Basic authentication mode in the Connect, Send, Forward, Reply and Reply All actions in the Email package and Email Trigger.

  • Ensure that the user credentials used to connect to the Control Room has the View content permission on the Bots folder.

    The Bot Scanner utility connects to your Control Room using these credentials.

  • Ensure that you meet the following system requirements for using the Bot Scanner:
    • Hardware requirements
      Processor 2.66 GHz or higher (64-bit)
      RAM 2 GB or higher
      Disc space 200 MB
    • Software requirements

      Operating systems: Windows 7 or later (32-bit or 64-bit)

Procedure

  1. Download the latest version of Bot Scanner from the Automation Anywhere Support site: Automation 360 Bot Scanner for EOL Features v33
  2. Extract the files from the zip file that you have downloaded and double-click the Automation_360_Bot_Scanner_For_EOL_Features.exe executable file to run the utility.
  3. In the Bot Scanner page, click the drop-down list and select Bots using Email action for Gmail with Basic authentication to select automations that use the Email server as Gmail.
    Scan automations using basic authentication to automate gmail
  4. Click Continue.
  5. In the Automation 360 Bot Scanner EOL features page, perform these steps:
    1. Enter the Control Room URL that you want to connect to
    2. Based on the authentication type configured in your Control Room, choose one of the following authentication methods in the Authentication Type field:
      Authentication type Steps
      Active Directory
      1. Enter the Username (Domain\\username).
      2. Enter the Password (domain user password).
      Database
      1. Enter the Username (Control Room database username).
      2. Enter the Password (Control Room database user password).
      Single Sign-On
      1. Enter the Username.
      2. Enter the API Key.
    3. Click Test connection.
      A connection success or failure message is displayed. Validate your credentials if the connection fails.
    4. In the Select destination path field, enter the location where you want to save the generated report.
    5. Click Scan bots.
      Connect to your Control Room and select destination path to download the report
    The scanner scans all the automations in your Control Room repository. After the scan is complete, a report (.CSV file) is available in the destination path you selected for your review.
    • If a .CSV file already exists in the output folder, a message is displayed that the previous .CSV file will be deleted. When you click Continue, a new .CSV file is generated.
    • If the previous .CSV file is in use, a message is displayed that the file cannot be deleted. Close the file and click Scan bots.
  6. Click Open report to analyze the report.
    The report contains the following details:
    • Task Bot name: Name of the Task Bot.
    • Line number: The line number of the Connect, Send, Forward , Reply, or Reply all actions that are using Basic authentication.

      For Email Trigger, the line number will be empty.

    • Package and action name: The Email package and action that is using Basic authentication to automate Gmail.
    • Searched text: The hostname or the domain name of the Gmail server for the respective action.
    • Action and review message: Use this information to understand the action that you have to perform or the information that you have to review for the corresponding action that is using the Basic authentication option.

      See Scanning messages for automations using Gmail with basic authentication.

    • Task Bot path: The path to the repository where the automation resides.

Next steps

After you identify the automations that are impacted in the Email package and Email Trigger, edit the impacted automations in the Bot editor and replace Basic authentication with the Control Room managed OAuth2 mode of authentication. Test the automations and ensure the result is same.