Skip to main content
Skip table of contents

Blue Cedar Connect Gateway 4.2.x Release Notes

About Blue Cedar Connect Gateway

The Blue Cedar Connect Gateway is an IKEv2 VPN gateway and a key component of Blue Cedar’s secure connectivity offering. The Blue Cedar Connect Gateway allows apps integrated with the Blue Cedar Accelerator for Secure Edge Connect to securely access network protected resources such as backend services and application data. With Blue Cedar’s secure connectivity offering, enterprise users can seamlessly connect to remote resources from any device, even one not controlled by MDM.

What's new

What's new in Blue Cedar Connect Gateway 4.2.6

What's new in Blue Cedar Connect Gateway 4.2.5

What's new in Blue Cedar Connect Gateway 4.2.3

  • Added a healthcheck REST API to the public interface. (BCC-239)
  • Added support for NDES 2016. (BCC-237)

Resolved issues

Resolved in Connect Gateway 4.2.6

​BCC-230​Fixed an issue where sometimes the underlying DNS configuration would not be updated with what was represented in the gateway configuration.
BCC-243Improved release file size.
BCC-255Fixed an issue where sessions were not being fully flushed.
BCC-285Fixed an issue where the client's IP address was not being displayed in the session.

Resolved in Connect Gateway 4.2.5

BCC-257​Fixed issue with verifying client certificate.​

Resolved in Connect Gateway 4.2.4

BCC-254​Fixed issue with file parsing during SCEP.​

Resolved in Connect Gateway 4.2.3

​BCC-225Fixed a bug where enrollment PIN was not emailed to the user during certificate enrollment.​
BCC-244Fixed a bug where authentication would incorrectly fail when using an LDAP auth-provider.

Open issues/limitations

  • You cannot currently modify a trusted certificate. To work around this limitation, first delete the certificate and add a new one. See Configuring AAA Public Key Infrastructure.
  • The gateway does not yet support the ability to add additional interfaces.
  • The gateway does not yet support the ability to configure network inactivity timeout.
  • Certificate enrollment is not currently supported with OAuth authentication.
  • The "auto" mode under the "ports" configuration is experimental.
  • Certificate enrollment email-pin is not yet supported when using LDAP authentication.


Online documentation is available at

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.