Firewall Requirements

Follow

Prior to configuring and onboarding users into the Clearlogin application, the firewall protecting the LDAP end point must be configured to allow traffic originating from Clearlogin destined for either TCP port 389 (LDAP) or 636 (LDAPS).

 

As of 11/2/15 we are going to be migrating LDAP queries from the previously used IP addresses to the following IP addresses:

  • 52.5.21.219
  • 52.22.22.126
  • 54.187.95.53
  • 54.187.96.193

Until you migrate your Identity Source configurations, the following IPs will still be used for requests. You must migrate by 1/1/2016 to ensure continued service.

  • 54.209.59.53
  • 54.84.156.93
  • 54.210.149.165
  • 54.86.39.216
  • 54.187.95.53
  • 54.187.96.193

*Please note that to ensure availability of service, all IPs included in the provided list must have access to the LDAP endpoint(s).

 

If you are using a proxy firewall such as something like zscaler or hardware domain based firewall you must allow these following domains through for our authentication libraries.

  • api-ping.intercom.io
  • nexus-websocket-a.intercom.io
  • nexus-websocket-b.intercom.io
  • fonts.googleapis.com
  • maxcdn.bootstrapcdn.com
  • admin.clearlogin.com
  • clearlogin-upload-prod.s3.amazonaws.com
  • js.intercomcdn.com
  • widget.intercom.io
  • ajax.googleapis.com
  • bam.nr-data.net
  • js-agent.newrelic.com
  • fareportal.clearlogin.com
  • www.google-analytics.com
Have more questions? Submit a request

Comments

Powered by Zendesk