> For the complete documentation index, see [llms.txt](https://coldbox-security.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://coldbox-security.ortusbooks.com/jwt/jwt-interceptions.md).

# JWT Interceptions

The JWT services announce these events. Listen to them with an [interceptor](https://coldbox.ortusbooks.com/the-basics/interceptors) to audit, log or react to token activity. Each event passes the keys below in `interceptData`.

| Event                                 | Announced when                                                                     | `interceptData` keys       |
| ------------------------------------- | ---------------------------------------------------------------------------------- | -------------------------- |
| `cbSecurity_onJWTCreation`            | A new token is generated for a user                                                | `token`, `payload`, `user` |
| `cbSecurity_onJWTInvalidation`        | A token is invalidated                                                             | `token`                    |
| `cbSecurity_onJWTValidAuthentication` | A valid token is parsed, tested and authenticated with the authentication services | `token`, `payload`, `user` |
| `cbSecurity_onJWTInvalidUser`         | The token's subject is not found: the user service returns null or an invalid user | `token`, `payload`         |
| `cbSecurity_onJWTInvalidClaims`       | The parsed token does not have the required claims                                 | `token`, `payload`         |
| `cbSecurity_onJWTExpiration`          | The parsed token has expired                                                       | `token`, `payload`         |
| `cbSecurity_onJWTStorageRejection`    | The parsed token is valid but is not in the permanent token storage                | `token`, `payload`         |
| `cbSecurity_onJWTValidParsing`        | The parsed token passed every validation but has NOT been authenticated yet        | `token`, `payload`         |

* `token` is the JWT string, `payload` is the decoded claims struct and `user` is the user the token belongs to.

## Example

{% code title="interceptors/SecurityAudit.cfc" %}

```javascript
component extends="coldbox.system.Interceptor"{

    function cbSecurity_onJWTCreation( event, interceptData ){
        // do what you like here
    }

}
```

{% endcode %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://coldbox-security.ortusbooks.com/jwt/jwt-interceptions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
