• State Verified Answer
  • Locked Locked
  • Replies 4 replies
  • Subscribers 64 subscribers
  • Views 3031 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 123308
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How to use nRF Connect v2.0 behind corporate SSL proxy?

Zoltan Mayer

Hi, Congratulations on releasing nRF Connect v2.0!
Unfortunately, I'm having trouble with adding apps behind corporate SSL proxy. Is there a workaround for this? Please consider adding feature for proxy configuration and adding trusted root CA certificates. Best regards, Zoltan

yarn-error.log

nrf_conn_err_msg.png

==============================================

UPDATE:

After some trial and error I found the correct configuration for Yarn. Some comments:

  • If you don't have Yarn installed, the .yarnrc file needs to be created manually and Yarn seems to require a certain file format (extra blank lines);
  • Depending on your SSL proxy, multiple cafile entries may be necessary;
  • The certificate file should have base-64 encoded X.509 format;
  • If you need to specify the domain in your proxy credentials, url-encode the separating backslash with %5C.

Config example for Windows:

.yarnrc

Parents
  • 0

    Hi,

    A pre-release (2.1.0-alpha.0) with improved support for proxies has been published on GitHub. Details can be found in pull request #104. This should detect the proxy server, and pass the proxy URL to Yarn, so that the https-proxy in .yarnrc should not be required. However, CA certificates are not automatically detected, so the cafile will still have to be set in .yarnrc if required.

    It would be great if you have time to test 2.1.0-alpha.0 and report back to us. When testing, try to remove https-proxy from .yarnrc to see if it is correctly detected.

Reply
  • 0

    Hi,

    A pre-release (2.1.0-alpha.0) with improved support for proxies has been published on GitHub. Details can be found in pull request #104. This should detect the proxy server, and pass the proxy URL to Yarn, so that the https-proxy in .yarnrc should not be required. However, CA certificates are not automatically detected, so the cafile will still have to be set in .yarnrc if required.

    It would be great if you have time to test 2.1.0-alpha.0 and report back to us. When testing, try to remove https-proxy from .yarnrc to see if it is correctly detected.

Children
No Data
Related