> For the complete documentation index, see [llms.txt](https://docs.oidc-spa.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oidc-spa.dev/integration-guides/backend-token-validation/mock-modes.md).

# Mock Modes

{% hint style="info" %}
This is the server-side mock mode.\
If you’re looking for the frontend mock mode, see [the project example for your stack](/integration-guides/example-setups.md).
{% endhint %}

`oidc-spa/server` provides two modes to facilitate backend unit testing.

These modes help you run tests in a reproducible way, without fetching the public key from a real IdP.

## Static identity

In this mode, `oidc-spa/server` ignores the provided token.\
It behaves as if every request comes from a user with the identity you define.

```typescript
bootstrapAuth({
    implementation: "mock",
    behavior: "use static identity",
    decodedAccessToken_mock: {
        sub: "123",
        name: "John Doe",
        email: "john.doe@gmail.com",
        realm_access: {
            roles: ["realm-admin", "support-staff"]
        }
    }
});
```

## Decode only

{% hint style="danger" %}
WARNING: If you accidentally ship this mode to production, it’s catastrophic.\
Everything will appear to work, but an attacker can impersonate anyone.
{% endhint %}

In this mode, `oidc-spa/server` decodes the access token payload, but skips all cryptographic validation.\
This is useful if you’ve saved tokens for unit tests and want those tests to keep working long after the tokens expire.

```typescript
bootstrapAuth({
    implementation: "mock",
    behavior: "decode only",
});
```


---

# 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://docs.oidc-spa.dev/integration-guides/backend-token-validation/mock-modes.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.