> For the complete documentation index, see [llms.txt](https://docs.empe.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.empe.io/develop/wallet-server/security-considerations.md).

# Security Considerations

## Authentication

* Header: `Authorization: Bearer <JWT>`
* Algorithms allowed: RS256, ES256
* Required claim: `sub` (used as user id/tenant key)
* Checks: `iat` must not be in the future; expired tokens yield `WWW-Authenticate: Bearer error="expired_token"`
* Public key source: `JWT_PROVIDER_PUBLIC_KEY` must be Base64‑encoded DER (SPKI)

Note: Swagger labels the auth scheme as `oneclick-jwt`, but requests must use the standard `Authorization` header.

## Debug Endpoints (local only)

If `ENABLE_DEBUG_SIGN_ENDPOINT=true`, the server exposes:

* POST `/auth/debug/keypair` → generate RS256/ES256 keys (DER), optionally persist to `.env`
* POST `/auth/debug/sign` → sign a short‑lived JWT for testing

Never enable these in production.

## Transport & Keys

* Always run behind HTTPS in production
* Protect private keys and `.env` files
* Rotate keys periodically; prefer short token TTLs for automation

## Multi‑Tenant Isolation

* Storage is scoped by `sub` → each user sees only their own DIDs and VCs
* Confirmation of flows is restricted to the user that initiated them


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.empe.io/develop/wallet-server/security-considerations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.