You can find the latest released version here. Download latest version from here:
The Queue-it Security Framework is used to ensure that end users cannot bypass the queue by adding a server-side integration to your server. It supports .NET Framework 4.0+.
When a user is redirected back from the queue to your website, the queue engine can attach a query string parameter (queueittoken) containing some information about the user.
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
The high level logic is as follows:
- User requests a page on your server
- The validation method sees that the has no Queue-it session cookie and no
queueittokenand sends him to the correct queue based on the configuration - User waits in the queue
- User is redirected back to your website, now with a
queueittoken - The validation method validates the
queueittokenand creates a Queue-it session cookie - The user browses to a new page and the Queue-it session cookie will let him go there without queuing again
To validate that the current user is allowed to enter your website (has been through the queue) these steps are needed:
- Providing the queue configuration to the KnownUser validation
- Validate the
queueittokenand store a session cookie
The recommended way is to use the Go Queue-it self-service portal to setup the configuration. The configuration specifies a set of Triggers and Actions. A Trigger is an expression matching one, more or all URLs on your website. When a user enter your website and the URL matches a Trigger-expression the corresponding Action will be triggered. The Action specifies which queue the users should be sent to. In this way you can specify which queue(s) should protect which page(s) on the fly without changing the server-side integration.
This configuration can then be downloaded to your application server as shown in the IntegrationConfigProvider example.
To validate that the user has been through the queue, use the KnownUser.ValidateRequestByIntegrationConfig() method.
This call will validate the timestamp and hash and if valid create a "QueueITAccepted-SDFrts345E-V3_[EventId]" cookie with a TTL as specified in the configuration.
If the timestamp or hash is invalid, the user is send back to the queue.
The KnownUser validation must be done on all requests except requests for static resources like images, css files and .... So, if you add the KnownUser validation logic to a central place like in Global.asax, then be sure that the Triggers only fire on page requests (including ajax requests) and not on e.g. image.
This example is using the IntegrationConfigProvider to download the queue configuration.
The following method is all that is needed to validate that a user has been through the queue:
private void DoValidation()
{
try
{
var customerId = "Your Queue-it customer ID";
var secretKey = "Your 72 char secrete key as specified in Go Queue-it self-service platform";
var queueitToken = Request.QueryString[KnownUser.QueueITTokenKey];
var currentUrlWithoutQueueITToken = Regex.Replace(Request.Url.AbsoluteUri, @"([\?&])(" + KnownUser.QueueITTokenKey + "=[^&]*)", string.Empty, RegexOptions.IgnoreCase);
// The currentUrlWithoutQueueITToken is used to match Triggers and as the Target url (where to return the users to)
// It is therefor important that the currentUrlWithoutQueueITToken is exactly the url of the users browsers. So if your webserver is
// e.g. behind a load balancer that modifies the host name or port, reformat the currentUrlWithoutQueueITToken before proceeding
var integrationConfig = IntegrationConfigProvider.GetCachedIntegrationConfig(customerId);
//Verify if the user has been through the queue
var validationResult = KnownUser.ValidateRequestByIntegrationConfig(currentUrlWithoutQueueITToken, queueitToken, integrationConfig, customerId, secretKey);
if (validationResult.DoRedirect)
{
//Adding no cache headers to prevent browsers to cache requests
Response.Cache.SetCacheability(HttpCacheability.NoCache);
Response.Cache.SetExpires(DateTime.UtcNow.AddHours(-1));
Response.Cache.SetNoStore();
//end
//Send the user to the queue - either because hash was missing or because is was invalid
Response.Redirect(validationResult.RedirectUrl,false);
HttpContext.Current.ApplicationInstance.CompleteRequest();
}
else
{
//Request can continue - we remove queueittoken form querystring parameter to avoid sharing of user specific token
if(HttpContext.Current.Request.Url.AbsoluteUri.Contains(KnownUser.QueueITTokenKey))
{
Response.Redirect(currentUrlWithoutQueueITToken, false);
HttpContext.Current.ApplicationInstance.CompleteRequest();
}
}
}
catch (Exception ex)
{
// There was an error validating the request
// Use your own logging framework to log the error
// This was a configuration error, so we let the user continue
}
}
If your application server (maybe due to security reasons) is not allowed to do external GET requests, then you have three options:
- Manually download the configuration file from Queue-it Go self-service portal, save it on your application server and load it from local disk
- Use an internal gateway server to download the configuration file and save to application server
- Specify the configuration in code without using the Trigger/Action paradigm. In this case it is important only to queue-up page requests and not requests for resources or AJAX calls. This can be done by adding custom filtering logic to Global.asax
or if using asp.net mvc by adding it as an ActionFilter on the page controllers
or if using aspx webforms then in the Master Page's Init() method
or with a proper filtering on the Global.asax Application_BeginRequest().
The following is an example of how to specify the configuration in code:
private void DoValidationByLocalEventConfig()
{
try
{
var customerId = "Your Queue-it customer ID";
var secretKey = "Your 72 char secret key as specified in Go Queue-it self-service platform";
var queueitToken = Request.QueryString[KnownUser.QueueITTokenKey];
var currentUrlWithoutQueueITToken = Regex.Replace(Request.Url.AbsoluteUri, @"([\?&])(" + KnownUser.QueueITTokenKey + "=[^&]*)", string.Empty, RegexOptions.IgnoreCase);
var eventConfig = new QueueEventConfig()
{
EventId = "event1", //ID of the queue to use
CookieDomain = ".mydomain.com", //Optional - Domain name where the Queue-it session cookie should be saved. Default is to save on the domain of the request
QueueDomain = "queue.mydomain.com", //Optional - Domain name of the queue. Default is [CustomerId].queue-it.net
CookieValidityMinute = 15, //Optional - Validity of the Queue-it session cookie. Default is 10 minutes
ExtendCookieValidity = false, //Optional - Should the Queue-it session cookie validity time be extended each time the validation runs? Default is true.
Culture = "en-US", //Optional - Culture of the queue ticket layout in the format specified here: https://msdn.microsoft.com/en-us/library/ee825488(v=cs.20).aspx Default is to use what is specified on Event
LayoutName = "MyCustomLayoutName" //Optional - Name of the queue ticket layout - e.g. "Default layout by Queue-it". Default is to use what is specified on the Event
};
//Verify if the user has been through the queue
var validationResult = KnownUser.ResolveQueueRequestByLocalConfig(currentUrlWithoutQueueITToken, queueitToken, eventConfig, customerId, secretKey);
if (validationResult.DoRedirect)
{
//Adding no cache headers to prevent browsers to cache requests
Response.Cache.SetCacheability(HttpCacheability.NoCache);
Response.Cache.SetExpires(DateTime.UtcNow.AddHours(-1));
Response.Cache.SetNoStore();
//end
//Send the user to the queue - either becuase hash was missing or becuase is was invalid
Response.Redirect(validationResult.RedirectUrl,false);
HttpContext.Current.ApplicationInstance.CompleteRequest();
}
else
{
//Request can continue - we remove queueittoken form querystring parameter to avoid sharing of user specific token
if (HttpContext.Current.Request.AbsoluteUri.Contains(KnownUser.QueueITTokenKey))
{
Response.Redirect(currentUrlWithoutQueueITToken);
HttpContext.Current.ApplicationInstance.CompleteRequest();
}
}
}
catch (System.Threading.ThreadAbortException)
{
//Response.Redirect will raise System.Threading.ThreadAbortException to end the exceution, no need to log the error
}
catch (Exception ex)
{
// There was an error validating the request
// Use your own logging framework to log the error
// This was a configuration error, so we let the user continue
}
}
If you have some static html pages (might be behind cache servers) and you have some ajax calls from those pages needed to be protected by KnownUser library you need to follow these steps:
- You are using v.3.5.1 (or later) of the KnownUser library.
- Make sure KnownUser code will not run on static pages (by ignoring those URLs in your integration configuration).
- Add below JavaScript tags to static pages:
<script type="text/javascript" src="//static.queue-it.net/script/queueclient.min.js"></script>
<script
data-queueit-intercept-domain="{YOUR_CURRENT_DOMAIN}"
data-queueit-intercept="true"
data-queueit-c="{YOUR_CUSTOMER_ID}"
type="text/javascript"
src="//static.queue-it.net/script/queueconfigloader.min.js">
</script>
- Use the following method to protect all dynamic calls (including dynamic pages and ajax calls).
private void DoValidation()
{
try
{
var customerId = "Your Queue-it customer ID";
var secretKey = "Your 72 char secrete key as specified in Go Queue-it self-service platform";
var queueitToken = Request.QueryString[KnownUser.QueueITTokenKey];
var currentUrlWithoutQueueITToken = Regex.Replace(Request.Url.AbsoluteUri, @"([\?&])(" + KnownUser.QueueITTokenKey + "=[^&]*)", string.Empty, RegexOptions.IgnoreCase);
// The currentUrlWithoutQueueITToken is used to match Triggers and as the Target url (where to return the users to)
// It is therefor important that the currentUrlWithoutQueueITToken is exactly the url of the users browsers. So if your webserver is
// e.g. behind a load balancer that modifies the host name or port, reformat the currentUrlWithoutQueueITToken before proceeding
var integrationConfig = IntegrationConfigProvider.GetCachedIntegrationConfig(customerId);
//Verify if the user has been through the queue
var validationResult = KnownUser.ValidateRequestByIntegrationConfig(currentUrlWithoutQueueITToken, queueitToken, integrationConfig, customerId, secretKey);
if (validationResult.DoRedirect)
{
//Adding no cache headers to prevent browsers to cache requests
Response.Cache.SetCacheability(HttpCacheability.NoCache);
Response.Cache.SetExpires(DateTime.UtcNow.AddHours(-1));
Response.Cache.SetNoStore();
//end
if (validationResult.IsAjaxResult)
{
//In case of ajax call send the user to the queue by sending a custom queue-it header and redirecting user to queue from javascript
Response.Headers.Add(validationResult.AjaxQueueRedirectHeaderKey, validationResult.AjaxRedirectUrl);
}
else
{
//Send the user to the queue - either becuase hash was missing or becuase is was invalid
Response.Redirect(validationResult.RedirectUrl,false);
}
HttpContext.Current.ApplicationInstance.CompleteRequest();
}
else
{
//Request can continue - we remove queueittoken form querystring parameter to avoid sharing of user specific token
if(HttpContext.Current.Request.Url.AbsoluteUri.Contains(KnownUser.QueueITTokenKey)
&& !string.IsNullOrEmpty(validationResult.ActionType))
{
Response.Redirect(currentUrlWithoutQueueITToken, false);
HttpContext.Current.ApplicationInstance.CompleteRequest();
}
}
}
catch (Exception ex)
{
// There was an error validating the request
// Use your own logging framework to log the error
// This was a configuration error, so we let the user continue
}
}