Skip to content
No description, website, or topics provided.
Branch: master
Clone or download
Latest commit 31e7ea4 Aug 7, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
sdk initial commit Jun 14, 2019 Update Aug 7, 2019
app.js bugfix- updating cookie Jul 19, 2019
contextProvider.js initial commit Jun 14, 2019
integrationConfigProvider.js initial commit Jun 14, 2019
package.json initial commit Jun 14, 2019
queueitHelpers.js bugfix- updating cookie Jul 19, 2019
queueitknownuser.bundle.js bugfix- updating cookie Jul 19, 2019


The Queue-it Security Framework is used to ensure that end users cannot reach to your protected backend routes without passing the virtual queue by performing a server-side validation before processing a request. This approach is using Cloudflare Workers and Cloudflare Workers KV to integrate a Cloudflare protected WebServer with Queue-it. This repository is containing a JavaScript file queueitknownuser.bundle.js you add as a Worker to your Cloudflare distribution to protect your traffic going through Cloudflare.


When a user makes a request to your backend Cloudflare will trigger queue-it Worker, the script validates the request and if it is needed, it will redirect the user to the queue. After waiting in the queue, the queue engine will redirect the user back to your end attaching a query string parameter (queueittoken) containing some information about the user to the URL. The most important fields of the queueittoken are:

  • q - the users' unique queue identifier
  • ts - a timestamp of how long this redirect is valid
  • h - a hash of the token

After the user is returned from the queue, the Worker script will let the user continue his request to your backend (without redirecting to the queue since the request has a valid queueittoken as querystring).


  • Browse to Cloudflare dashboard -> Workers -> Workers KV and add a new KV, name it IntegrationConfigKV
  • Browse to Cloudflare dashboard -> Workers -> Launch Editor -> Add script and paste queueitknownuser.bundle.js
  • Go to the added script select the Resources tab -> KV Namespaces click Add Binding and for VARIABLE NAME enter IntegrationConfigKV and for NAMESPACE you should be able to select IntegrationConfigKV which you had added before
  • Add routes you need to be protected by Queue-it (e.g. PROTECTED.YOURDOMAIN.COM/*)
  • Search for QUEUEIT_CUSTOMERID and QUEUEIT_SECRETKEY in queueitknownuser.bundle.js replace their values with your customerId and secretKey found in Go Queue-It self-service platform
  • Setup the Publish web endpoint (e.g. [PROTECTED ROUTE]/?__push_queueit_config) in Integration -> Overview -> Settings
  • Setup Trigger and Action in Go Queue-it and once ready click Integration -> Overview -> Show/Hide Instructions and click the Push Now button

Please contact queue-it support for further information and instructions.

You can’t perform that action at this time.