# queueit/knownuser

> Using queueit known user to manage magento integration

`composer require queueit/knownuser`

Canonical URL: https://packagento.com/queueit/knownuser

## At a glance

- **Vendor**: queueit (https://packagento.com/queueit.md)
- **Latest version**: 1.3.6 — released 2026-05-26
- **Pricing**: Free
- **Package type**: Magento 2 module
- **Status**: active, accepting new buyers

## Installation

Packagento is licence-gated, so even free packages need a licence on a project before Composer can resolve them.

1. **Sign in or create an account** at https://packagento.com/customer/account/.

2. **Add the package to your account.** Open https://packagento.com/queueit/knownuser and complete the free checkout. A licence is minted automatically.

3. **Create or pick a project, then activate the licence on it.**
   - Projects represent the Magento installs you deploy to. Manage them at https://packagento.com/projects/.
   - Activate the new licence on the project you'll deploy this package to. Activation is what generates the Composer credentials scoped to that project.

4. **Add the project credentials to your Magento codebase.**

   Grab the project's public + private key from https://packagento.com/projects/ (open the project, then its Credentials tab), and add them to `auth.json`:

   ```json
   {
     "http-basic": {
       "packagento.com": {
         "username": "ppk_live_...",
         "password": "psk_live_..."
       }
     }
   }
   ```

   Add the Packagento Composer repository to `composer.json`:

   ```json
   {
     "repositories": [
       { "type": "composer", "url": "https://packagento.com" }
     ]
   }
   ```

5. **Install and apply.**

   ```bash
   composer require queueit/knownuser:*
   bin/magento setup:upgrade
   bin/magento setup:di:compile
   bin/magento cache:flush
   ```

## What it does

Using queueit known user to manage magento integration

## README

Server-side implementation of the QueueIT queueing system. This will put customers into a queue before they can enter the site.
**FPC modules could prevent this module from working properly.**(Please contact queue-it for the practices of handling FPC scenario.)

## Installation
How to install the module using different methods.


### Manual
First clone this repository inside your Magento2 `app/code` folder like below:

```bash
cd <your Magento 2 install dir>/app/code
git clone https://github.com/queueit/KnownUser.V3.MagentoV2.git Queueit/KnownUser
```
Afterwards install the extension:
```
cd <your Magento 2 install dir>
php bin/magento setup:upgrade
```
Doing so you can run the below command. It should show *Queueit_KnownUser* as an installed module:
 
```bash
bin/magento module:status
```
If Queueit_KnownUser was listed as Disabled module run the below command to enable it
```
php bin/magento module:enable Queueit_KnownUser
php bin/magento setup:upgrade
```

### Composer

Install queueit module using composer
```
$ composer require queueit/knownuser
```
*Enter your [`authentication`](https://devdocs.magento.com/guides/v2.3/install-gde/prereq/connect-auth.html) keys. Your public key is your username; your private key is your password.*
Afterwards install it with
```
$ php bin/magento setup:upgrade
```
Doing so you can run the below command it should show *Queueit_KnownUser* as an installed module 
```
$ bin/magento module:status
```
You can find an official help about how to install a Magento extension [here](https://devdocs.magento.com/extensions/install/).
## Configuration
After installing the module, go to the below menu and enable the module, enter your CustomerId and Secret Key which you have got from QueueIT.
`Stores -> Configuration -> Services -> Queueit KnownUser`

In here 

- **Enabled**: Enable/disable module execution. If enabled this will generally give a redirect on every request. So it is advanced to enable it only before an event is starting.
- **CustomerID**: This is usually your account name
- **Secret Key**: This is the secret key found in QueueIt: `Account -> Security -> Known User (tab) -> Default secret key`
- **How are the configs updated**: The way changes on QueueIT's side are requested
  - Push: Configure url in QueueIT. Postback url is `{{store_url}}/rest/V1/queueit/integrationinfo/`
  - Manual: To Update configuration manually or to see the current configuration: `Content -> QueueIt KnownUser -> Admin`. You can see the current config at this page and also upload confugartion file for updating it. 


## FPC  (Protecting ajax calls on static pages)
If you have Full Page Cache enabled you should add queue-it javascript to your pages as below :
1. Make sure KnownUser code will not run on static pages (by ignoring those URLs in your integration configuration).
2. Add below JavaScript tags to all static pages : 
    You can add this tag in the header files : `...\vendor\magento\module-theme\view\frontend\templates\html\header.phtml`
    ```
    <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>
    ```
3. Add some triggers for your dynamic ajax calls you want to queue users on.

## Recent Versions

| Version | Released |
|---|---|
| 1.3.6 | 2026-05-26 |
| 1.3.5 | 2021-08-26 |
| 1.3.4 | 2021-02-03 |
| 1.3.3 | 2020-12-08 |
| 1.3.0 | 2019-07-29 |
| 1.2.0 | 2018-11-16 |
| 1.0.0 | 2018-02-13 |

## Dependencies

### Require

| Package | Constraint |
|---|---|
| ext-json | * |
| queueit/knownuserv3 | ^3.6.1 |

### Require (dev)

| Package | Constraint |
|---|---|
| magento/framework | * |
| magento/module-store | * |
| psr/log | 1.1.3 |

## Quality

Latest release (1.3.6) fails the Packagento QA pipeline. Verdicts below are per-cell (Magento line × PHP version) for the matrixed tools, and run-once for the static / security tiers.


### Compatibility

Each Magento line is installed on its supported PHP versions, then the module is built (DI compile + static-content deploy). Cells show passed / failed / untested; staircase gaps render as `–`.

| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | Pass | Pass | – | – |
| 2.4.8 | – | Pass | 1 | – |
| 2.4.9 | – | – | 1 | 1 |


### Code Quality

Advisory checks against the module's source. Never affect the Compatibility verdict — a phpcs finding can't make a module incompatible.

#### Static Analysis

Coding standards (phpcs), mess detection (phpmd), copy-pasted code (cpd), PHP cross-version compatibility, composer.json validity. Each runs once for the whole module.

| Tool | Status | Findings | Summary |
|---|---|---|---|
| PHPCS | Fail | 88 | 6 errors, 82 warnings (ruleset: Magento2) — 34 auto-fixable with phpcbf |
| PHPMD | Warning | 3 | 3 rule violations (UnusedFormalParameter:2, MissingImport:1) |
| Cpd | Pass | 0 |  |
| Composer validate | Info | 1 | valid; 1 advisory note (composer validate --strict) |

#### PHPStan

Type-checks the module against a real Magento install. Re-runs per Magento + PHP version because resolvable symbols differ between releases.

| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | 24 | 24 | – | – |
| 2.4.8 | – | 24 | 28 | – |
| 2.4.9 | – | – | 28 | 28 |


### Tests

Unit and integration suites run per Magento + PHP cell. Test failures speak to the module's behaviour, not its compatibility with a line, so they're reported here separately.

#### Unit Tests

| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | – | – |
| 2.4.8 | – | N/A | N/A | – |
| 2.4.9 | – | – | N/A | N/A |

#### Integration Tests

| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | – | – |
| 2.4.8 | – | N/A | N/A | – |
| 2.4.9 | – | – | N/A | N/A |


### Security

Dependency-advisory audit (composer audit) plus a source malware scan. A malware detection fails the version outright.

| Tool | Status | Findings | Summary |
|---|---|---|---|
| Composer audit | Pass | 0 |  |
| Malware scan | Pass | 0 |  |

## Licence and pricing

Free. A licence is still minted on checkout and bound to your project for Composer access — no payment step.

Refundable within 14 days of first purchase via https://packagento.com/account/refunds/.

## Install via Claude Code or any MCP client

The Packagento MCP server can run the licence + project + Composer steps above in one tool call:

```
purchase_and_install_packages(
  composer_names=["queueit/knownuser"],
  project_id="proj_xxx"
)
```

This handles cart, checkout, licence minting, project activation, and writes auth.json credentials. Connect a client with `claude mcp add packagento https://mcp.packagento.com`. Full setup at https://packagento.com/docs/mcp-setup.

## Vendor

queueit is a Magento 2 vendor on Packagento. See https://packagento.com/queueit.md for their full catalogue.