SELECT PRODUCT

Introduction
Onboarding
What is CloudBees Feature Management?
Use cases
Introduction
Installing client-side SDKs
Installing server-side SDKs
Environments
About feature flags
Creating a feature flag
Feature flag settings
Deleting a feature flag
Embedded feature flags
Multiplatform feature flags
Flag freeze levels
Feature flag configuration update flow
Configuration values
Toggling flags on & off
Audiences
Custom properties
Percentage rollouts
Scheduled rollouts
Target groups
Flag dependencies
Grouping flags by feature
Configuration as Code
Verbose logging
Local testing
Microservices testing
User space error handler
Flag impressions
Fetched handler
Integrating with Jira
Managing users
Managing teams and permissions
Managing applications
Managing billing plans
Audit log
SAML single sign-on
Two-factor authentication
Allow/Disallow domains
Secret mode
Support policies
Supported platforms
Terms and services
Open Source Software Attributes

Allowlist domains

This section lists the URLs that are used by the SDK to properly communicate with our outbound backend servers.

The following URLs are used by the SDK:

  • https://statestore.rollout.io/ - GET request to verify the state of new feature flag and customer properties.

  • https://conf.rollout.io/ - GET request to retrieve the latest configuration.

  • https://x-api.rollout.io/ - GET/POST request send to CloudBees Feature Management servers to indicate a new version is running, or a new state is discovered.

  • https://analytic.rollout.io/ - POST request to CloudBees Feature Management analytics servers, to see impressions on the dashboard.

  • https://push.rollout.io/ - Server Sent Events that get notifications upon a change in the configuration. No special firewall rules are required.

The following third-party URL is used by the SDK:

  • https://notify.bugsnag.com/ - POST request to Bugsnag tool. SDK error monitoring and reporting tool.

Two-factor authentication
Secret mode