--- title: "System operation - token flow" slug: "system-operation-token-flow-v7-0" description: "Learn about token generation, authentication, and entitlement tokens for secure client-server communication and user access management." tags: ["Token Generation", "Token Renewal", "Tokens"] updated: 2026-09-21T20:31:32Z published: 2026-09-21T20:31:32Z canonical: "support.appgate.com/system-operation-token-flow-v7-0" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.appgate.com/llms.txt > Use this file to discover all available pages before exploring further. # System operation - token flow --- ## Token generation and flow ### Initial setup Before the first authentication, the client has a URL to one of the Controllers and the Certificate Authority (CA) certificate. These are either installed automatically with the client or entered manually by the user, who then downloads the CA certificate. The client uses the CA certificate in all communications to verify the authenticity of the Controller or Gateway. ![Diagram illustrating network components including client, public network, controller, and gateway.](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/slide01.png?sv=2026-02-06&spr=https&st=2026-11-21T21%3A55%3A34Z&se=2026-11-21T22%3A55%3A34Z&sr=b&sp=r&sig=pGy4SKrsaBbAO1rGBBgPvT%2B4WyK2k8w1%2FFDxv1WO0VQ%3D) ### Authentication When signing in, the user enters credentials such as a username and password. The Controller verifies the credentials against a user directory. If the client does not already have a random ID, it generates one and sends it along with the credentials. ![Diagram illustrating user credentials flow between client, controller, and endpoint server.](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/slide02.png?sv=2026-02-06&spr=https&st=2026-11-21T21%3A55%3A34Z&se=2026-11-21T22%3A55%3A34Z&sr=b&sp=r&sig=caLnaV6JQbp0h5V5MZ0lC3qoFY18LDA4CVOPVPpNbcU%3D) On successful authentication, the Controller replies with a claims token. The claims token is issued to a Distinguished Name (DN) that includes both the user's DN and the client ID. This DN identifies the session throughout the system. ### Entitlement tokens 1. The client uses the claims token to request entitlement tokens. ![Diagram illustrating client-server communication over public and private networks with tokens.](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/slide03.png?sv=2026-02-06&spr=https&st=2026-11-21T21%3A55%3A34Z&se=2026-11-21T22%3A55%3A34Z&sr=b&sp=r&sig=CV29EOjVLdZCl%2FMM6lIIXzoC2c01AokB%2FWNx14UhBnQ%3D) ![Diagram illustrating client computer interaction with controller and gateway in a network.](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/slide04.png?sv=2026-02-06&spr=https&st=2026-11-21T21%3A55%3A34Z&se=2026-11-21T22%3A55%3A34Z&sr=b&sp=r&sig=b%2BxAI21KkL4t0Y0Uz6UpKqqELSjEejDCYRvOxzu2d0Q%3D) 1. The Controller queries its internal database to find all services the user is entitled to and replies with entitlement tokens — one per Site. ![Diagram illustrating the Controller replying to the client computer either Entitlement tokens.](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/slide05.png?sv=2026-02-06&spr=https&st=2026-11-21T21%3A55%3A34Z&se=2026-11-21T22%3A55%3A34Z&sr=b&sp=r&sig=fljeIyflRzOJlEcBRIxJq0xtFYvkB8T2RMbjwZxjVG4%3D) 1. The client generates an RSA key pair. ![Diagram illustrating network components including client computer, controller, and gateway connections.](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/slide06.png?sv=2026-02-06&spr=https&st=2026-11-21T21%3A55%3A34Z&se=2026-11-21T22%3A55%3A34Z&sr=b&sp=r&sig=6O4O3lBRWBmH8tX9b0J6xaf1%2FkWM2aoa58pv%2Bya1Ld0%3D) 1. The client sends a certificate signing request to the Controller, based on the claims token and public key. ![Diagram illustrating client-server communication with tokens and network connections.](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/slide07.png?sv=2026-02-06&spr=https&st=2026-11-21T21%3A55%3A34Z&se=2026-11-21T22%3A55%3A34Z&sr=b&sp=r&sig=AD2VudGX6SHbTHaB4t8TPfyoCsCnyLRLxoJG7jGOfSE%3D) 1. The Controller replies with a certificate for the client, issued by the CA to the same DN as in the claims token. This DN includes both the user's DN and the client ID. ![Diagram illustrating client-server communication with certificates and network components.](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/slide08.png?sv=2026-02-06&spr=https&st=2026-11-21T21%3A55%3A34Z&se=2026-11-21T22%3A55%3A34Z&sr=b&sp=r&sig=hWkg90rNGZnTTAaM10Z0CM2Tw%2F1qhzLyPj5kuYFafM0%3D) --- ## Connecting to the right Gateway The client establishes a TLS tunnel to one Gateway in each Site, using the client certificate for client-side TLS authentication. ![Diagram illustrating client computer connections to various network components and certificates.](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/slide09.png?sv=2026-02-06&spr=https&st=2026-11-21T21%3A55%3A34Z&se=2026-11-21T22%3A55%3A34Z&sr=b&sp=r&sig=Fj1qnXS9rdC1vNMn6og3NbNMYhp36pquyH2O89j5UnA%3D) The client then sends the claims token, a number of untrusted device claims, and a Site-specific entitlement token to each connected Gateway. ![Diagram illustrating client computer interactions with controllers and gateways in a network.](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/slide10.png?sv=2026-02-06&spr=https&st=2026-11-21T21%3A55%3A34Z&se=2026-11-21T22%3A55%3A34Z&sr=b&sp=r&sig=AIyJZdTG830sWBLzx6Z5RJbL%2BAv896fInh2pfcNvgeE%3D) --- ## Per-user firewalling Each Gateway translates the claims token, client claims, and entitlement token into a list of firewall rules that apply to that user on that client device at that specific time. ![Diagram illustrating network components including client computer, public network, and firewall rules.](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/slide11.png?sv=2026-02-06&spr=https&st=2026-11-21T21%3A55%3A34Z&se=2026-11-21T22%3A55%3A34Z&sr=b&sp=r&sig=%2FDExg%2B8%2BrzPvrQehExG7Uj60nVakN2clkVOmST1BNXs%3D) The client can then send IP packets to endpoint servers through the TLS tunnel, provided the firewall rules allow it. ![Diagram illustrating network components including client, gateway, and endpoint server connections.](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/slide13.png?sv=2026-02-06&spr=https&st=2026-11-21T21%3A55%3A34Z&se=2026-11-21T22%3A55%3A34Z&sr=b&sp=r&sig=WrIWddMrLeeg9g%2B1Ogzq9GyjONi2X7wu2327H48XG6o%3D) --- ## Step-up authentication A user interaction can be defined within a condition to enforce additional security requirements — for example, requiring the user to re-enter their password before accessing a protected resource. If the client sends an IP packet that is not currently allowed by the firewall rules but may become allowed depending on run-time conditions, the Gateway detects this and checks whether a user interaction is associated with the destination. ![Diagram illustrating network components including client, gateway, and endpoint server connections.](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/slide14.png?sv=2026-02-06&spr=https&st=2026-11-21T21%3A55%3A34Z&se=2026-11-21T22%3A55%3A34Z&sr=b&sp=r&sig=iV3IrrAB8vnotJYZuM19OApB8Cw3ethAlmEnvasuGCU%3D) The Gateway sends a user interaction to the client over a WebSocket connection that the client keeps open for the session. The user interaction can display instructions or trigger specific actions in the client, such as initiating a new authentication. ![Diagram illustrating client computer connections to public and private networks with authentication processes.](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/slide15.png?sv=2026-02-06&spr=https&st=2026-11-21T21%3A55%3A34Z&se=2026-11-21T22%3A55%3A34Z&sr=b&sp=r&sig=jygOG%2FqRUYgSIzsnp0WYV17Ef39nMSTZPqnAJ7yKaZA%3D) The Controller verifies the user interaction and replies with a new claims token confirming the user has completed the required authentication. The client sends the new claims token to the Gateway, which re-evaluates the conditions in the entitlement token and produces new firewall rules. ![Diagram illustrating client-server communication with tokens and network pathways.](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/slide16.png?sv=2026-02-06&spr=https&st=2026-11-21T21%3A55%3A34Z&se=2026-11-21T22%3A55%3A34Z&sr=b&sp=r&sig=bQfkP6jMOCfRA6KKmf4fnsCWnvRjML9XFKSBcEC8up8%3D) With the new firewall rules in place, the Gateway allows packets to the previously blocked destination. ![Diagram illustrating network components including client, gateway, and endpoint server interactions.](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/slide17.png?sv=2026-02-06&spr=https&st=2026-11-21T21%3A55%3A34Z&se=2026-11-21T22%3A55%3A34Z&sr=b&sp=r&sig=QIPjAuigvbWbgljCKGWAuM02ecqW1G9It0skANEqMaQ%3D) Depending on the type of user interaction, the user is presented with one of the following: - **OTP prompt.** The user provides a one-time password (OTP), which the Controller verifies using the OTP provider specified in the condition. The Controller issues a new claims token with an updated OTP claim, and the client sends it to the Gateway. - **Reason for access prompt.** The user enters a reason for access. The text is sent to the Gateway as an untrusted claim. - **Password prompt.** The user enters their password. The Controller validates it using the identity provider specified in the user interaction, which can be the same identity provider used for authentication or a different one. - **Remediation message.** The user is shown instructions for gaining access — for example, updating antivirus software. When the user resolves the issue, the client sends an updated value for the relevant client-side claim, such as antivirus status, to the Gateway. - **Informational message.** The user is shown a message explaining why access cannot be granted at this time. --- ## Updating entitlements by revoking tokens An administrator can force a user's claims and entitlement tokens to renew in real time. When an immediate token renewal is invoked, the token revocation list is updated and pushed to all Gateways. The Gateway notifies the client that tokens are expiring shortly, and the client retrieves new tokens to replace them. The user is unaware of this renewal process. ![Diagram illustrating network components including admin computer, controller, and tokens.](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/slide18.png?sv=2026-02-06&spr=https&st=2026-11-21T21%3A55%3A34Z&se=2026-11-21T22%3A55%3A34Z&sr=b&sp=r&sig=9cNV86RhfPZJRf5o4idLuGz6ZEF1I1kzuFd9L8Dmr54%3D)