Testing Cycle Access Token URLs

Testing Cycle Access Token URLs

Cycle requires an access token associated with a license in order to use the application.  

It is necessary for the Cycle application to communicate with Azure B2C to secure this access token. Certain firewall or proxy configurations on your organization's network may possibly prevent the authentication process from working properly and block you from acquiring an access token.

The URLs below need to traffic to be whitelisted in order to complete the authentication process and secure an access token:
  1. http://cyclelabsproduction.b2clogin.com/
  2. http://app.cyclelabs.io/
  3. https://graph.windows.net
  4. https://graph.microsoft.com/
  5. https://content.product.cyclelabs.io
  6. https://data.product.cyclelabs.io

We have developed a simple Cycle test that you can execute using the Cycle command line interface (Cycle-CLI) to determine if network traffic to the URLs listed above is being blocked on your organization's network.

If any of the URLs do not return the expected status when the test is executed, please work with your IT Network and Security teams to have traffic to the URLs whitelisted on your organization's network.

Test Cycle Authentication URLs


1. Ensure Cycle is installed on your device. Take note of the install location. The default location is "C:\Program Files (x86)\CycleLabs\Cycle\cycle-cli.exe".

2. Download the URLTest.zip file (attached at the bottom of this article) to your device.

3. Extract the URLTest.zip file to a location on your device where your user has write permission. In my example below, I extracted the file in my "Downloads" directory.

4. Open a PowerShell session and navigate to the directory where you extracted the URLTest.zip file.

5. Run the following command in PowerShell:
 & "C:\Program Files (x86)\CycleLabs\Cycle\cycle-cli.exe" -u cycle_user -p URLPingTest.cycproj Ping_Required_URLs.feature
 (Note: this assumes you installed Cycle to the default Program Files (x86) directory. You will need to update the PowerShell command accordingly if you installed Cycle to a different location)

6. You should see output similar to what is captured in the screenshot below. This shows the status code returned by the HTTP GET request sent to each endpoint and compares it to the expected status.

7. If you did not get the expected response from the HTTP request or if any URLs timed out in giving a response, please work with your IT Network and Security teams to allow network traffic between your device and the URL(s) that did not return the expected response.

    • Related Articles

    • Cycle 2 Install FAQ

      The Cycle install process and post-install authentication process has changed as of the release of Cycle 2.9.2. This process applies to Cycle 2.9.2 and all future versions of the Cycle 2 Application. This article contains frequently asked questions ...

    • Cycle 2 Install Guide

      This article covers the process of installing the Cycle Client on your device and the steps required to authenticate using your Cycle Cloud credentials. The release of Cycle 2.9 kicked off our incremental move toward the cloud, leveraging more modern ...

    • How to Make Cycle Proxy Aware

      Certain firewall or proxy configurations may possibly prevent the Cycle authentication process from working properly, and Cycle will not be able to secure an access token. The purpose of this article is to describe the process for making Cycle proxy ...

    • How to resolve "Windows Protected Your PC" message when installing Cycle

      Occasionally, when first running the Cycle installer, the following error message may be encountered. To resolve this issue, simply click on the "More info" link. That will display more information about the app that is being prevented from starting. ...