> For the complete documentation index, see [llms.txt](https://docs.giize.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.giize.com/ticket-dashboard-en/user-guide/openvpn.md).

# OpenVPN

This page answers one question: **among the users requesting OpenVPN, who actually needs a TS ticket created?**

To answer it, the page cross-checks three sources:

* **SDP** — who has an open ticket requesting OpenVPN
* **ACL** — who already has a valid IP
* **TS Jira** — who already has an active TS ticket

Anyone who already has an IP or an active TS does not need a new one. Cross-checking these three systems by hand takes a lot of time and easily creates duplicates — that is why this page exists.

![OpenVPN page](/files/dkAGg8U8znrns709reca)

## Start here: press Quick refresh

**Quick refresh** runs the whole pipeline: read SDP, read TS, check ACL, then cross-check. It takes **2–5 minutes**.

If any session has expired, the dashboard tells you exactly which one and asks for the matching PIN + OTP. See [Logging in to the systems](/ticket-dashboard-en/user-guide/dang-nhap.md).

The other buttons are for when you only need to rerun part of it:

| Button            | What it runs                                                  |
| ----------------- | ------------------------------------------------------------- |
| **Quick refresh** | the entire pipeline                                           |
| **Reload data**   | just redraws the existing results, without calling any system |
| **Fetch TS**      | only re-reads TS Jira                                         |
| **Check ACL**     | only re-checks IPs on ACL                                     |

## Reading the results: 5 groups

After it finishes, each user falls into exactly one group. This is the most important part of the page:

| Group              | Meaning                                | What you need to do                                     |
| ------------------ | -------------------------------------- | ------------------------------------------------------- |
| **Need create**    | has an SDP ticket, no valid IP, no TS  | ✅ **Create a TS** — this is the group that needs action |
| **Already has IP** | already has a valid IP                 | close the SDP ticket, do not create anything            |
| **Has active TS**  | already has an active TS               | wait, do not create a duplicate                         |
| **TS only**        | has a TS but no SDP ticket found       | check whether the SDP ticket was closed too early       |
| **Unknown**        | ACL could not be checked for this user | run **Check ACL** again                                 |

{% hint style="info" %}
Only the **Need create** group needs any action from you. The other four groups are there so you can see why those users are *not* on the list of ones to create.
{% endhint %}

### The "Old IP (invalid)" column

In the Need create table, this column shows a struck-through IP when a user has an IP but it no longer falls within the valid range — usually an old IP from another office or one that has been revoked. These users still need a new IP.

The valid IP range is set in [Settings](/ticket-dashboard-en/user-guide/settings.md) → OpenVPN.

## Creating a TS ticket

1. Tick the users in the **Cần tạo TS ticket** (Need to create TS ticket) table — or press **Select all**
2. Press **Create selected (n)**
3. Review the list in the confirmation box
4. Confirm

The dashboard creates each TS ticket and reports the result for each user. If any user fails, you can retry just those users without starting over.

{% hint style="warning" %}
This action **creates real tickets** on TS Jira. Re-read the list in the confirmation box before you press it.
{% endhint %}

## The Cookies label

Shows which session is still valid:

* **ACL: session** — the ACL session is still usable
* **TS: active** — the TS session is still valid

When the label turns red, you need to log in to that session again before running the pipeline.

## Technical details

How the pipeline works under the hood: [OpenVPN Pipeline](/ticket-dashboard-en/feature-guides/openvpn-pipeline.md).