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 aware so that Cycle authenticate traffic can be routed through a web proxy.
The steps in this article only apply if you or your organization are using a web proxy and the machine Cycle is running on is behind the proxy. Please confirm with your organization's IT network team whether or not your machine is behind a web proxy.
Before continuing with proxy server troubleshooting, be sure that the Azure B2C URLs are whitelisted on your network and any network security solutions such as Zscaler are allowing Cycle SSL traffic. Details for these items can be found in the Cycle 2 Install Guide.
If you are using Cycle on a machine that is behind a web proxy, then Cycle may not be able to communicate with the Azure B2C server after entering your credentials in the Cycle Cloud login page.
If this occurs, you will see the "Authentication complete" message, but after returning to Cycle you will still see the "The default web browser will be opened..." message:
Steps to Make Cycle Proxy Aware
1) Open the Cycle application and select Edit->Preferences in the menu at the top of the application. Please note, you do not need to be authenticated in order to complete these steps.
2) Scroll to the bottom of the Application Preferences screen until you see the Advanced->Server Tuning option.
3) Server Tuning gives Cycle users the opportunity to define Java run-time parameters that Cycle will use when starting the application. This allows us to pass proxy server information to the Cycle java process.
4) Enter the following parameters into the "Server Tuning" text box:
-Dhttps.proxyHost=[proxy server IP] -Dhttps.proxyPort=[proxy server port] -Dhttps.nonProxyHosts=localhost
** Note: You must replace the proxyHost and proxyPort values with the proxy server IP address and proxy server port relevant to your network. Please get this information from your IT Network team.**
Here is an example of what the parameters might look like (note: your proxy server IP and proxy server port will be different)
-Dhttps.proxyHost=127.0.0.1 -Dhttps.proxyPort=3128 -Dhttps.nonProxyHosts=localhost
5) After copying the parameters into the "Server Tuning" text field, click the blue "X" in the upper right section of the Application Preferences screen. Then close and re-open Cycle.
6) The new proxy settings in the Server Tuning section will be applied when Cycle restarts. Web traffic initiated by Cycle should now flow through your proxy server with the exception of local web traffic to localhost that is used by several of the Cycle functions.