BACK TO CONNECTORS

Queue-it's Tencent Connector v4 uses Tencent Cloud to integrate a Tencent protected WebServer with Queue-it.

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

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.

The following diagram shows the Queue-it logic with an edge Connector.

1. User requests a page.
2. The validation method sees that user has no Queue-it session cookie and no Queue-it token and sends him to the correct waiting room with a valid token based on the configuration.
3. User waits in the queue.
4. User is navigated back to your website, now with a valid token.
5. The validation method validates the token and creates a Queue-it session cookie.
6. The user browses to a new page and the Queue-it session cookie will let him proceed without queuing again.

You can read more about Queue-it's edge compute integrations on our blog, and can find the full list of integrations on our Connectors page.

To integrate using the Queue-it Tencent Connector v4, 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 V4 Connector Download Access (Tencent CDN admin must have access to the secure Queue-it V4 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 setting. 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).