BACK TO CONNECTORS

Queue-it's Tencent Connector v5 uses Tencent Cloud to integrate a Tencent-protected web server with Queue-it.

This page is intended to give a high-level technical overview of the Tencent Connector v5. To prevent malicious actors from compromising the security of our customers' high-profile sales and registrations, we host our in-depth Connector documentation in private repositories for versions v4 and up.

If you need more detailed integration documentation than this page offers, connect with one of our technical experts who can understand your use case and determine the optimal setup for your tech stack.

• Request received
  • User request reaches the Queue-it Connector on your edge infrastructure.
• Connector evaluation
  • The Queue-it Connector checks:
    • Does the request target a protected path?
    • Does the visitor have a valid Queue-it token?
• Call to Queue-it for decision logic
  • If the request is protected and no valid token is present, the Connector calls Queue-it to determine if the visitor needs to be queued based on your Queue-it configuration (e.g. traffic levels are above your threshold, rules allowing certain users to bypass the queue, waiting room is active or idle, etc.)
• Redirect to Queue-it
  • If the visitor needs to be queued, they are redirected with an HTTP 302 to a waiting room on Queue-it’s infrastructure.
  • If the visitor does not need to be queued (e.g. in a 24/7 Protection setup with low inflow), they proceed directly to the protected page without the need for a 302 redirect.
• Access granted
  • When it’s their turn, they are redirected back to your site with another HTTP 302 and given a signed token. With the signed token, the visitor’s request proceeds to the protected part of your site, and they continue their user journey without queuing.

To integrate using the Queue-it Tencent Connector v5, you will need:

• An active Queue-it account
• An active Tencent account
• Queue-it admin available (Someone with GO Queue-it Platform access and familiarity with the account configuration settings)
• Tencent CDN and EdgeOne admin available (Someone with access to the customer Tencent Cloud Control account who is also familiar with existing CDN and EdgeOne configurations (rule engine, edge functions, etc.))
• Tencent v5 Connector Download Access (Tencent CDN admin must have access to the secure Queue-it v5 Connector GitHub repository, which is not publicly accessible)
• A non-production Tencent CDN configuration that can be used for implementing and testing the new Queue-it Tencent Connector.

The Tencent Connector consists of the following components:

1. Queue-it EdgeOne – code provided by Queue-it that enables the waiting room protection
2. Edge Functions Variables – these variables hold key values that are used by EdgeOne
3. Edge Functions Triggers – triggers that define the scope of EdgeOne protection
4. Rule Engine – enables EdgeOne to perform actions like IP address checks, allowing specific IPs to bypass the queue
5. Queue-it Integration Configuration – configuration information (JSON format) is created in the GO Queue-it Platform using actions & triggers settings. Currently, the auto-pull method is not supported, so you must hardcode this configuration into the code uploaded to EdgeOne. This means that you need to update the code each time you change your configuration settings.

1. Configure waiting rooms, actions, and triggers in Queue-it and create a configuration file
2. Create EdgeOne
3. Set up Tencent Connector
4. Create Engine Rules

Queue-it's actions and triggers framework gives you a high degree of flexibility in determining what aspects of your site are covered by the virtual waiting room (see How Queue-it Works).