Opens in FoxAuth Cloud, in your project. You sign in first, or create a free account.
auth.acme-notes.app
AAcme Notes
Sign in
Email
Password
Sign in
or
Continue with Google
The FoxAuth sign-in page
Password, or a provider button
Then back to your site, signed in
Your server keeps a secret and trades a one-time code for tokens, so this is the simplest and the safest sign-in.
On your own server, this needs no setting switched on.
How it works, step by step
Person
Yourserver
FoxAuth
1Clicks “Sign in”
2Sends to sign-in
3Signs in
4One-time code
5Code + secret
6Signed in
FoxAuth
A message
The browser is sent on
Carries a token
1The person clicks “Sign in” on your site.
2Your server sends the browser to the FoxAuth sign-in page.
3The person types a password or uses Google. Only FoxAuth sees the password.
4FoxAuth sends the person back to your callback address with a one-time code.
5Your server trades the code for tokens and shows its secret. The browser never sees this.
6Your server starts a session, and the person is in.
Good to know
Plain http is allowed only for localhost. Every other address needs https.
Keep the secret on the server, in an environment variable, never in the code.
Prompt for your agent
Paste it into Claude, Cursor or another coding agent. It covers your code and the console setup. The prompt is in English.
Add sign-in through FoxAuth to my web app with a server (work out the stack from the code).
Flow: Authorization Code + PKCE, a confidential application (client_secret_basic), refresh tokens.
Callback: http://localhost:3000/callback. After sign-out: http://localhost:3000.
The server’s issuer is <your project's issuer, on its Overview> and its discovery document is <issuer>/.well-known/openid-configuration.
If the FoxAuth administrative MCP is connected, use client_create with applicationType web, grantTypes authorization_code and refresh_token, tokenEndpointAuthMethod client_secret_basic. Otherwise ask me to press the button for this in the console at https://auth.foxauth.dev/admin.
Keep the secret only on the server, in an environment variable.
The browser did not allow copying. Select the text and copy it.
Under the hood: OpenID Connect · Authorization Code + PKCE · client_secret_basic · refresh tokens
Opens in FoxAuth Cloud, in your project. You sign in first, or create a free account.
auth.acme-notes.app
AAcme Notes
Sign in
Email
Password
Sign in
or
Continue with Google
The FoxAuth sign-in page
Password, or a provider button
Then back to your app, signed in
There is nowhere to keep a secret, so PKCE protects the sign-in: a one-time check string that only this browser tab knows.
On your own server, this needs no setting switched on.
How it works, step by step
Person
Yourbrowserapp
FoxAuth
YourAPI
1Clicks “Sign in”
2Sign-in + PKCE
3Signs in
4One-time code
5Code + check string
6Call with the token
FoxAuth
A message
The browser is sent on
Carries a token
1The person clicks “Sign in” in your app.
2Your app sends the browser to sign in, with a fingerprint of the check string.
3The person signs in on the FoxAuth page.
4FoxAuth sends the person back to your app with a one-time code.
5Your app trades the code for tokens and shows the check string itself. A stolen code is useless without it.
6Your app calls your API with the access token.
Good to know
There is no secret, and that is fine: PKCE does the protecting.
Refresh tokens live a shorter time in a browser than on a server.
Plain http is allowed only for localhost.
Do not keep tokens in localStorage if the library can hold them in memory.
Prompt for your agent
Paste it into Claude, Cursor or another coding agent. It covers your code and the console setup. The prompt is in English.
Add sign-in through FoxAuth to my single-page app (work out the framework from the code).
Flow: Authorization Code + PKCE, a public application with no secret, refresh tokens.
Callback: http://localhost:5173/callback. After sign-out: http://localhost:5173. Allowed origin (CORS): http://localhost:5173.
The server’s issuer is <your project's issuer, on its Overview> and its discovery document is <issuer>/.well-known/openid-configuration.
If the FoxAuth administrative MCP is connected, use client_create with applicationType web, tokenEndpointAuthMethod none, corsOrigins http://localhost:5173. Otherwise ask me to press the button for this in the console at https://auth.foxauth.dev/admin.
The browser did not allow copying. Select the text and copy it.
Under the hood: OpenID Connect · Authorization Code + PKCE · public application · refresh tokens
Opens in FoxAuth Cloud, in your project. You sign in first, or create a free account.
auth.acme-notes.app
AAcme Notes
Sign in
Email
Password
Sign in
or
Continue with Google
The FoxAuth sign-in page, in the system browser
Then “you can close this tab”, from your app
Sign-in opens in the system browser, and the code comes back to your app on a local address, on any port.
On your own server, this needs no setting switched on.
How it works, step by step
Person
Yourapp
FoxAuth
1Starts sign-in
2Opens the browser
3Signs in
4Code to 127.0.0.1
5Code + PKCE
FoxAuth
A message
The browser is sent on
Carries a token
1The person clicks “Sign in” or runs your login command.
2Your app opens the system browser on the sign-in page, with PKCE.
3The person signs in, in a browser they trust.
4FoxAuth sends the code to http://127.0.0.1, on whatever port your app listens on right now.
5Your app trades the code for tokens.
Good to know
One callback address covers every port, so you never register each run.
There is no secret: the app is in the person’s hands and can be taken apart.
An AI agent that runs on the person’s computer and signs in as them is set up exactly the same way.
Do not use an embedded WebView for sign-in.
Prompt for your agent
Paste it into Claude, Cursor or another coding agent. It covers your code and the console setup. The prompt is in English.
Add sign-in through FoxAuth to my native app (mobile, desktop or CLI: work it out from the code).
Flow: Authorization Code + PKCE, a public application with no secret, sign-in in the system browser.
Callback: http://127.0.0.1/callback, on a free port chosen at each run.
The server’s issuer is <your project's issuer, on its Overview> and its discovery document is <issuer>/.well-known/openid-configuration.
If the FoxAuth administrative MCP is connected, use client_create with applicationType native, tokenEndpointAuthMethod none, redirectUris http://127.0.0.1/callback. Otherwise ask me to press the button for this in the console at https://auth.foxauth.dev/admin.
The browser did not allow copying. Select the text and copy it.
Under the hood: OpenID Connect · Authorization Code + PKCE · loopback redirect (RFC 8252)
2FoxAuth returns a short code and an address. The device shows both.
3The person opens the address on their phone, types the code and signs in as usual.
4Meanwhile the device asks every few seconds whether the code was confirmed.
5As soon as the person has signed in, the device gets its tokens.
Good to know
The person needs a second screen: a phone or a computer.
The code is short and expires quickly. There is nothing to store.
Respect the polling interval and handle slow_down.
Prompt for your agent
Paste it into Claude, Cursor or another coding agent. It covers your code and the console setup. The prompt is in English.
Add sign-in through FoxAuth to my app on a device with no keyboard.
Flow: Device Authorization Grant (RFC 8628), a public application with no secret.
Show the code and the address from the response on screen, then poll /token at the interval the response gives.
The server’s issuer is <your project's issuer, on its Overview> and its discovery document is <issuer>/.well-known/openid-configuration.
If the FoxAuth administrative MCP is connected, use client_create with applicationType native, grantTypes urn:ietf:params:oauth:grant-type:device_code, tokenEndpointAuthMethod none. Otherwise ask me to press the button for this in the console at https://auth.foxauth.dev/admin.
The browser did not allow copying. Select the text and copy it.
Under the hood: OAuth 2.0 Device Authorization Grant (RFC 8628)
4Your API checks the token’s signature against the project’s public keys. It does not call FoxAuth on every request.
Good to know
The token speaks for the program. No person is in it.
If the secret leaks, issue a new one in the console.
Cache the token until it expires. Do not ask for a new one on every call.
Prompt for your agent
Paste it into Claude, Cursor or another coding agent. It covers your code and the console setup. The prompt is in English.
Set up calls to my API from a background service through FoxAuth.
Flow: Client Credentials, a confidential application (client_secret_basic), no person involved.
The server’s issuer is <your project's issuer, on its Overview> and its discovery document is <issuer>/.well-known/openid-configuration.
If the FoxAuth administrative MCP is connected, use client_create with grantTypes client_credentials, tokenEndpointAuthMethod client_secret_basic. Otherwise ask me to press the button for this in the console at https://auth.foxauth.dev/admin.
The browser did not allow copying. Select the text and copy it.
Opens in FoxAuth Cloud, in your project. You sign in first, or create a free account.
Nobody sees a screen: this is between programs
Declare the API in your project, and FoxAuth writes it into each token as the recipient, so a token meant for another API is refused.
On your own server, this needs no setting switched on.
How it works, step by step
Yourapp
FoxAuth
YourAPI
AnotherAPI
1Token for your API
2Recipient: your API
3Accepted
4Refused
FoxAuth
Outside your control
A message
Carries a token
A refusal
1Your app asks for a token and names the API it is for.
2FoxAuth issues a token with the recipient written in it.
3Your API sees itself as the recipient and accepts the call.
4The same token fails at another API: the recipient does not match.
Good to know
An API address is unique within a project.
Your app names the API when it asks for a token.
Your API can ask FoxAuth whether a token is still valid, and an app can revoke a token it no longer needs, once a super administrator has switched introspection and revocation on.
Refuse a token with another recipient (aud), even when its signature is valid.
Prompt for your agent
Paste it into Claude, Cursor or another coding agent. It covers your code and the console setup. The prompt is in English.
Protect my API with FoxAuth tokens.
The API is declared as the resource https://api.example.com.
In the API, check the token signature against the project’s jwks_uri, the issuer (iss) and the recipient (aud = https://api.example.com). Apps must send resource=https://api.example.com when they ask for a token.
The server’s issuer is <your project's issuer, on its Overview> and its discovery document is <issuer>/.well-known/openid-configuration.
If the FoxAuth administrative MCP is connected, use resource_declare with the address https://api.example.com. Otherwise ask me to press the button for this in the console at https://auth.foxauth.dev/admin.
The browser did not allow copying. Select the text and copy it.
Under the hood: OAuth 2.0 Resource Indicators (RFC 8707) · audience-bound tokens · introspection (RFC 7662) · revocation (RFC 7009)
A programOn your own server
Other developers register their own apps on your platform
1The developer’s app sends its details to the registration address.
2FoxAuth stores it as an application and returns its ID and a management token.
3People sign in to that app like any other. The consent page says the app registered itself.
4Later the app changes or removes its own registration with the management token.
Good to know
It is a setting for the whole server, switched on by a super administrator.
For MCP clients, prefer a description address (metadata URL): the MCP specification deprecates self-registration for them.
Switching registration off stops new registrations. Apps already registered keep working.
Prompt for your agent
Paste it into Claude, Cursor or another coding agent. It covers your code and the console setup. The prompt is in English.
Explain how an outside developer registers an app at my FoxAuth project’s registration_endpoint (from discovery), and how they update it with the registration access token.
The server’s issuer is <your project's issuer, on its Overview> and its discovery document is <issuer>/.well-known/openid-configuration.
Ask me to press the button for this in the console at https://auth.foxauth.dev/admin.
The browser did not allow copying. Select the text and copy it.
Under the hood: Dynamic Client Registration (RFC 7591) · Registration Management (RFC 7592)
An AI agentReady on FoxAuth Cloud
Claude, Cursor or ChatGPT connect to your MCP server
Opens in FoxAuth Cloud, in your project. You sign in first, or create a free account.
auth.acme-notes.app
AAcme Notes
Claudeasks to act on your behalf
Read your notes
Add new notes
Deny
Allow
The sign-in page, then a consent page
It names the agent and your MCP server
The person allows or refuses
Declare your MCP server in your project, and an agent connects after a person signs in, with no registration: it introduces itself by the address of its own description.
2Your server answers that sign-in is needed, and names FoxAuth.
3The agent gives the address of its description (a metadata URL). It registers nothing beforehand.
4The person signs in and sees which agent is asking for access.
5FoxAuth issues a token that works only for your server.
6The agent works with your server on the person’s behalf.
Good to know
The token is bound to your server. It does not work at anyone else’s MCP server.
Your server checks the token itself, against the project’s public keys.
Agents introduce themselves by a description address only while a super administrator has switched that on in the server’s settings. An agent that cannot host one needs registration switched on instead.
Do not build client registration in your MCP server.
Prompt for your agent
Paste it into Claude, Cursor or another coding agent. It covers your code and the console setup. The prompt is in English.
Add authorization through FoxAuth to my MCP server.
The server is declared as the resource https://mcp.example.com.
Serve /.well-known/oauth-protected-resource with authorization_servers set to the project’s issuer. Answer a request with no token with 401, WWW-Authenticate and resource_metadata.
Check the signature, iss, and aud = https://mcp.example.com.
The server’s issuer is <your project's issuer, on its Overview> and its discovery document is <issuer>/.well-known/openid-configuration.
If the FoxAuth administrative MCP is connected, use resource_declare with the address https://mcp.example.com. Otherwise ask me to press the button for this in the console at https://auth.foxauth.dev/admin.
The browser did not allow copying. Select the text and copy it.
Under the hood: MCP Authorization · OAuth 2.1 · Protected Resource Metadata · Client ID Metadata Document
An AI agentReady on FoxAuth Cloud
Your agent acts in the person’s Google, GitHub or Slack
Opens in FoxAuth Cloud, in your project. You sign in first, or create a free account.
auth.acme-notes.app
AAcme Notes
GoogleConnect your account
Your agent can then use it on your behalf, through FoxAuth.
Cancel
Connect
A page that names the service, for example Google
The person connects the account and agrees
Later, a list of their connected accounts
The person connects their account once, and after that the agent gets access through FoxAuth and keeps nobody’s tokens itself.
On your own server, this needs no setting switched on.
How it works, step by step
Person
AIagent
FoxAuth
Google,GitHub,Slack
1Connects Google
2Access
3Exchanges its token
4Google token
5Acts
FoxAuth
Outside your control
A message
Carries a token
1The person connects their account once and agrees.
2Google grants access. FoxAuth stores it encrypted.
3The agent shows its own token and asks for this person’s Google access.
4FoxAuth hands over a Google token for this person only.
5The agent reads mail, creates a task or posts in a channel as the person.
Good to know
You provide an app at that service: its ID and secret.
The person sees their connected accounts and can disconnect any of them. The agent loses access at once.
The agent only gets a token for the person who connected the account.
Do not keep the Google token longer than one request.
Prompt for your agent
Paste it into Claude, Cursor or another coding agent. It covers your code and the console setup. The prompt is in English.
Teach my agent to act in Google for the signed-in person through FoxAuth.
Google is added to the project as a connected service.
The agent gets a Google token by exchanging its own token at /token (grant_type urn:ietf:params:oauth:grant-type:token-exchange). If the account is not connected yet, show the person the connect link.
The server’s issuer is <your project's issuer, on its Overview> and its discovery document is <issuer>/.well-known/openid-configuration.
If the FoxAuth administrative MCP is connected, use connected_service_create for Google. Otherwise ask me to press the button for this in the console at https://auth.foxauth.dev/admin.
The browser did not allow copying. Select the text and copy it.
Under the hood: OAuth 2.0 Token Exchange (RFC 8693) · token vault
Opens in FoxAuth Cloud, in your project. You sign in first, or create a free account.
auth.foxauth.dev
FoxAuth administration
Claudeasks to act as you
See your projects and applications
Create and change applications
Deny
Allow
The administrator sign-in page
A page that names the agent asking to act as you
The agent does in FoxAuth what you do in the console, with the same rights and the same checks and no special way in.
On your own server, switch on in Settings: mcp.enabled
How it works, step by step
You
AIagent
FoxAuth
1“Create an application”
2Administrator sign-in
3client_create
4Same checks
5Written to the trail
6Result
FoxAuth
A message
Happens inside one box
1You ask the agent in plain words.
2The agent connects to /mcp. You sign in and allow it to act.
3The agent calls a tool: the same one behind the console button.
4Rights, checks and plan limits are the console’s own.
5The audit trail records who allowed it and which agent did it.
6The agent gets the answer and tells you what was done.
Good to know
The agent acts with exactly your rights.
The most dangerous acts, such as deleting a project, stay in the console.
It is off until a super administrator switches it on in the server’s settings. FoxAuth Cloud has it on.
The agent connects through FoxAuth’s own MCP client or as an application a super administrator has permitted; an app that registered itself never can.
Prompt for your agent
Paste it into Claude, Cursor or another coding agent. It covers your code and the console setup. The prompt is in English.
Connect to the FoxAuth administrative MCP of the server whose console is at https://auth.foxauth.dev/admin. The address is the /mcp path of that server, and sign-in goes through OAuth.
After signing in, call whoami and tell me which projects I can reach.
Before any high-risk action, ask me again.
The browser did not allow copying. Select the text and copy it.
Under the hood: MCP · OAuth 2.1 protected resource
6Your app gets the same tokens as after a password sign-in.
Good to know
All four providers are on the Free plan.
You provide an ID and a secret from the provider’s console.
Microsoft on Free accepts accounts from any organisation. Limiting sign-in to one company’s directory is in the section for companies.
Your app does not need to change.
Prompt for your agent
Paste it into Claude, Cursor or another coding agent. It covers your code and the console setup. The prompt is in English.
Add sign-in through Google to my FoxAuth project.
Tell me where in Google Cloud Console to create the OAuth client and which callback address to give it, then connect it in FoxAuth.
The server’s issuer is <your project's issuer, on its Overview> and its discovery document is <issuer>/.well-known/openid-configuration.
If the FoxAuth administrative MCP is connected, use federation_provider_create for Google. Otherwise ask me to press the button for this in the console at https://auth.foxauth.dev/admin.
The browser did not allow copying. Select the text and copy it.
Opens in FoxAuth Cloud, in your project. You sign in first, or create a free account.
auth.acme-notes.app
AAcme Notes
Sign in
Email
Password
Sign in
or
Continue with Google
The project’s sign-in page, the first time
Then your app, as before
Someone not allowed sees a page that says so
Put the app behind your proxy. The proxy asks FoxAuth about each request before it reaches the app, so people sign in to your project and the app does not change.
On your own server, this needs no setting switched on.
How it works, step by step
Person’sbrowser
Yourproxy
Yourapp
FoxAuth
1Opens the app
2Asks the project
3Sends to sign-in
4Signs in
5Back to /_foxauth/callback
6Yes, this is Anna
7With X-Auth-* headers
FoxAuth
Your reverse proxy
A message
The browser is sent on
1The person opens your app. The request reaches your proxy first.
2Your proxy asks the project whether this request may go through, before the app sees it.
3Nobody is signed in yet, so the project sends the browser to its sign-in page.
4The person signs in to the project, or is already signed in to it.
5The project sends the browser back to /_foxauth/callback on your app’s own address, and the app’s sign-in cookie is set there.
6On the next request the project checks your rules for that path and answers yes, with who the person is.
7Your proxy lets the request through to your app, with the person’s id, email and groups in X-Auth-* headers.
Good to know
Make sure the app is reachable only through your proxy. A request that reaches it another way skips the check.
Your app does not change. It can read who the person is from the X-Auth-* headers.
The Connect step gives the configuration for Caddy, Traefik or nginx, ready to paste.
Each path can be open to the members of chosen groups, to everyone in the project, to anyone, or to no one, and can add conditions: a network, some hours, an attribute, a recent sign-in.
There is nothing to switch on, and it is on every plan.
Prompt for your agent
Paste it into Claude, Cursor or another coding agent. It covers your code and the console setup. The prompt is in English.
Put sign-in in front of my web app at https://app.example.com, behind my reverse proxy (work out Caddy, Traefik or nginx from my configuration). Only members of the group I name may open it.
Create the app behind the proxy in FoxAuth, then add the configuration it gives to my proxy.
The server’s issuer is <your project's issuer, on its Overview> and its discovery document is <issuer>/.well-known/openid-configuration.
If the FoxAuth administrative MCP is connected, use behind_proxy_app_create. Otherwise ask me to press the button for this in the console at https://auth.foxauth.dev/admin.
Make sure the app is reachable only through the proxy, so nobody can reach it without the check.
The browser did not allow copying. Select the text and copy it.
Under the hood: Forward auth · OpenID Connect · Authorization Code + PKCE
An AI agentReady on FoxAuth Cloud
Protect an MCP server without auth code
1Your problem
AIagentYourproxyYourMCPserver
Your MCP server is open until you write auth code.→
Opens in FoxAuth Cloud, in your project. You sign in first, or create a free account.
auth.acme-notes.app
AAcme Notes
Claudeasks to act on your behalf
Read your notes
Add new notes
Deny
Allow
The sign-in page, then a consent page
It names the agent and your MCP server
The person allows or refuses
Put your MCP server behind your proxy. The proxy asks FoxAuth to check the token on each request, and the scopes the tool needs, so the server itself needs no auth code.
1The agent calls your MCP server. The request reaches your proxy first.
2Your proxy asks the project to check the request, before your MCP server sees it.
3There is no token yet. The project answers 401 and names itself, and your proxy passes the answer back.
4The person signs in and sees which agent is asking for access.
5The project issues a token that works only for your MCP server.
6The agent calls the tool again, with the token.
7The project checks the token and the scopes this tool needs, and answers yes.
8Your proxy passes the request on, with who is calling and their scopes in X-Auth-* headers.
Good to know
When you declare the API, answer “Who checks tokens?” with “Your proxy”. Its Connect gives the configuration for Caddy, Traefik or nginx, ready to paste.
The Access tab of the API’s page says which scopes each tool needs, and who may call the API at all: some groups, an attribute, a network, some hours. One tool can have its own groups, network or hours on top. A client that lacks a scope is told exactly which scopes to ask for.
The project publishes the description agents look for (the protected resource metadata), so your MCP server serves nothing for sign-in.
A revoked token keeps working at the proxy until it expires, unless the API issues opaque tokens. Keep the lifetime short.
Tokens bound to a key (DPoP or a certificate) are refused at the proxy, because the proxy cannot check the key.
Make sure your MCP server is reachable only through your proxy. Without a condition, anyone who can sign in to the project can get a token for it. It is on every plan.
To ask for a code from an authenticator app, or a new sign-in every so often, before an agent connects, set it on the Access tab of the API’s page.
Prompt for your agent
Paste it into Claude, Cursor or another coding agent. It covers your code and the console setup. The prompt is in English.
Check tokens for my MCP server at https://mcp.example.com/mcp in my reverse proxy (work out Caddy, Traefik or nginx from my configuration), so the server needs no auth code.
Declare it in FoxAuth as an API whose tokens the proxy checks (checkedBy proxy), with its scopes. Then set its tools table: each tool and the scopes it needs. Add the configuration its Connect gives to my proxy.
The server’s issuer is <your project's issuer, on its Overview> and its discovery document is <issuer>/.well-known/openid-configuration.
If the FoxAuth administrative MCP is connected, use resource_declare with checkedBy proxy, then resource_update with tools. Otherwise ask me to press the button for this in the console at https://auth.foxauth.dev/admin.
Make sure the MCP server is reachable only through the proxy, so nobody can reach it without the check.
The browser did not allow copying. Select the text and copy it.
Under the hood: Forward auth · MCP Authorization · OAuth 2.1 · Protected Resource Metadata (RFC 9728)
Add a condition to a path of an app behind your proxy: only from the addresses you list. Someone elsewhere is turned away before they are asked to sign in.
On your own server, this needs no setting switched on.
How it works, step by step
Person’sbrowser
Yourproxy
Yourapp
FoxAuth
1Opens the app
2Asks, with the address
3Not from this network
4Opens it at the office
5Yes, this is Anna
6With X-Auth-* headers
FoxAuth
Your reverse proxy
A message
A refusal
1The person opens your app from a café. The request reaches your proxy first.
2Your proxy asks the project and passes the address it saw, with the project’s proxy key.
3The address is not one you listed, so the project says no, before any sign-in.
4At the office the same request comes from an address you listed.
5The project checks the address and the rest of your rules, and answers yes.
6Your proxy lets the request through to your app.
Good to know
Your proxy must pass the address it saw and show the project’s proxy key. The app’s Connect page gives the lines to add, and a test that a browser cannot choose its own address.
A network condition cannot be saved until a check has arrived with the key and a public address, so one save cannot lock everyone out.
Conditions add up down the paths: a condition on / applies to every path under it.
A VPN or a residential proxy can still get around a list. It slows an attacker down; it does not stop one.
When a super administrator turns on network facts from FoxTrust, “From where” can also keep out Tor, commercial VPNs, hosting and other countries. A matching address is refused, or asked to sign in again. The next answer shows how.
The FoxAuth console is never behind these conditions. It is on every plan.
Prompt for your agent
Paste it into Claude, Cursor or another coding agent. It covers your code and the console setup. The prompt is in English.
Let people open my app behind the proxy only from my office network, 203.0.113.0/24.
Issue the project’s proxy key in the console, add the lines the app’s Connect page gives to my proxy, then add a network condition to the rule for /.
The server’s issuer is <your project's issuer, on its Overview> and its discovery document is <issuer>/.well-known/openid-configuration.
If the FoxAuth administrative MCP is connected, use behind_proxy_app_update with rules[].conditions. Otherwise ask me to press the button for this in the console at https://auth.foxauth.dev/admin.
Issue the proxy key in the console: an agent never receives it.
The browser did not allow copying. Select the text and copy it.
Under the hood: Forward auth · X-Forwarded-For
A personReady on FoxAuth Cloud
Keep Tor, VPNs and other countries away from a path
Opens in FoxAuth Cloud, in your project. You sign in first, or create a free account.
From Tor, a listed VPN, hosting or another country: a page saying the page cannot be opened from where they are
Or, if you chose it: a new sign-in, with a code if you asked for one
From an ordinary address in a country you allow: the app, as before
Add network facts to “From where” on a path of an app behind your proxy: not from Tor, a commercial VPN or hosting, and only from the countries you choose. Your server learns what an address is from FoxTrust’s signed snapshot, and a condition never sends the address anywhere.
1Your server downloads FoxTrust’s snapshot of what is known about internet addresses: a full file once a day and an update every hour. It checks the signature before using it.
2Someone opens /admin of your app through Tor. The request reaches your proxy first.
3Your proxy asks the project and passes the address it saw, with the project’s proxy key.
4The project looks the address up in the server’s own copy of the snapshot. For this check, the address is not sent anywhere.
5The snapshot marks the address as a Tor exit, so the project says no, before any sign-in.
6At home, in a country you allow, the same request comes from an ordinary address.
7The address passes. The project checks the rest of your rules and answers yes.
8Your proxy lets the request through to your app.
Good to know
A super administrator turns on “Network facts from FoxTrust” in Settings → Integrations. Each server then downloads a file of about 13 MB once a day and an update every hour.
People’s addresses are looked up only inside your server. FoxTrust learns only that the file was downloaded.
Commercial VPN covers only the VPN services FoxTrust lists, not a company VPN. Hosting or a cloud also covers content networks and some companies’ own exits. iCloud Private Relay is not kept out.
Countries come from DB-IP (IP Geolocation by DB-IP, CC BY 4.0). An address with no known country is refused by “Only from” and passes “Not from”.
A matching address is refused, or asked to sign in again within the minutes you choose, with a code from an authenticator app if you tick it. An API checked at the proxy can only refuse.
If the download is off or the snapshot is more than 26 hours old, the path is closed until a fresh one loads, and the console marks it. Check access shows what the snapshot says about an address.
Your proxy must pass the address it saw with the project’s proxy key, as for a list of networks. It is on every plan.
Prompt for your agent
Paste it into Claude, Cursor or another coding agent. It covers your code and the console setup. The prompt is in English.
Keep Tor, commercial VPNs and hosting away from /admin of my app behind the proxy, and let people open the whole app only from Germany and Austria.
Check that network facts are current for the app. Then add a network condition with a facts part to the rule for /admin (categories tor, vpn and hosting) and one to the rule for / (countries: only DE and AT), each refusing a matching address.
The server’s issuer is <your project's issuer, on its Overview> and its discovery document is <issuer>/.well-known/openid-configuration.
If the FoxAuth administrative MCP is connected, use behind_proxy_app_get (addresses.networkFacts says whether they are current), then behind_proxy_app_update with a facts part on a network condition in rules[].conditions. Otherwise ask me to press the button for this in the console at https://auth.foxauth.dev/admin.
Network facts are an instance setting for a super administrator: networkFacts.enabled. To explain a refusal, look the address up with network_facts_lookup.
The browser did not allow copying. Select the text and copy it.
Under the hood: Forward auth · Signed IP snapshot (FoxTrust) · DB-IP country data
Opens in FoxAuth Cloud, in your project. You sign in first, or create a free account.
The same refusal page as before: nothing changes for the person
Open the person in Users: their Activity tab shows every sign-in, every failed one, and every time an app behind your proxy or an API refused them, with the reason and what they saw.
On your own server, this needs no setting switched on.
How it works, step by step
Person
FoxAuth
Administrator
1Tries to open the wiki
2Refused
3Opens the person’s Activity
4Reason and what they saw
FoxAuth
A message
A refusal
1Anna opens the wiki, an app behind your proxy, and signs in.
2The wiki’s rules do not let her open /admin. She sees a page saying she cannot open it.
3Anna writes to support. Support opens her in Users and goes to her Activity tab.
4The tab shows the refusal at 10:14, three times, “Not in the groups that may open /admin”, and a link to check it against today’s rules.
Good to know
Kept for every project: sign-ins with the application, the method, the network address, FoxTrust’s country and network kind when network facts are on, and the browser and system.
Beside the address, its network owner, region and city, looked up at FoxTrust’s API while “Look up network owner and location at FoxTrust” is on in Settings → Integrations. It is on by default, and FoxTrust keeps none of the addresses.
Failed sign-ins are kept only where the account was found: a wrong password or code, a locked or deactivated account, a missing code or an unverified address.
At your proxy the person’s address is kept only when your proxy proves it with the project’s proxy key. An API row never has one.
Everything is kept 90 days, survives a lock, and goes with the person and the project. Reading it is recorded in the audit trail.
It is recorded up to a minute late. A super administrator can turn recording off in Settings.
After you narrow an app’s or an API’s rules, its Access tab lists who it refused in the last 24 hours, with the time you saved between those refused before and after.
Prompt for your agent
Paste it into Claude, Cursor or another coding agent. It covers your code and the console setup. The prompt is in English.
Why was anna@acme.com refused by the Wiki app today?
The server’s issuer is <your project's issuer, on its Overview> and its discovery document is <issuer>/.well-known/openid-configuration.
If the FoxAuth administrative MCP is connected, use project_user_list to find her, then project_user_activity_list with outcome refused; after a rule change, behind_proxy_app_refusal_list or resource_refusal_list. Otherwise ask me to press the button for this in the console at https://auth.foxauth.dev/admin.
The browser did not allow copying. Select the text and copy it.
Under the hood: Sign-in decisions · Forward auth decisions
A personReady on FoxAuth Cloud
Find people who no longer use an app
1Your problem
Administrator
Nobody can tell who still uses an app before taking access away.→
Opens in FoxAuth Cloud, in your project. You sign in first, or create a free account.
Nothing: people never see this
Filter Users by Last active: it counts a sign-in, a token renewal and every request your proxy lets through, so someone working on an open session is never called inactive.
On your own server, this needs no setting switched on.
How it works, step by step
Administrator
FoxAuth
1Filters Users
2People not active
3Opens a person
FoxAuth
A message
1Before a quarterly clean-up, Kai filters Users by “Last active: Not in the last 90 days”.
2The list shows who has not signed in, renewed tokens or been let in by your proxy in 90 days. Someone who opens the wiki every day on an old session is not on it.
3Kai opens one of them. Profile lists the apps and APIs they used in the last 90 days, and their Activity tab shows each day.
Good to know
Last active counts a sign-in, a token renewal and a request your proxy let through, once a day.
What a person used is kept one entry per app, or per API and application, and day, with the first and last time. An API’s entry names the tools of its table they called. Never an address.
“Not in the last 90 days” is read from monthly marks: a month that overlaps the 90 days counts as active, so nobody is called inactive by rounding.
Use is recorded up to five minutes late, kept 90 days, and goes with the person and the project.
Monthly active people count people your proxy let in, so a plan’s limit on them counts them too.
Prompt for your agent
Paste it into Claude, Cursor or another coding agent. It covers your code and the console setup. The prompt is in English.
Who in the Acme project has not been active in the last 90 days, and what did they last use?
The server’s issuer is <your project's issuer, on its Overview> and its discovery document is <issuer>/.well-known/openid-configuration.
If the FoxAuth administrative MCP is connected, use project_user_list with lastActive not90, then project_user_activity_list for one of them. Otherwise ask me to press the button for this in the console at https://auth.foxauth.dev/admin.
The browser did not allow copying. Select the text and copy it.
Under the hood: Activity marks · Forward auth decisions
Opens in FoxAuth Cloud, in your project. You sign in first, or create a free account.
auth.acme-notes.app
AAcme Notes
Sign in
Email
Password
Sign in
or
Continue with Google
The sign-in page, saying the app asks for a fresh sign-in
Then the page they opened
Add a condition to a path such as /admin: ask to sign in again when the sign-in is older than you allow. A sign-in from yesterday no longer opens it.
On your own server, this needs no setting switched on.
How it works, step by step
Person’sbrowser
Yourproxy
Yourapp
FoxAuth
1Opens /admin
2Asks the project
3Sign in again
4Signs in
5Yes, a fresh sign-in
6With X-Auth-* headers
FoxAuth
Your reverse proxy
A message
The browser is sent on
1The person signed in this morning and now opens /admin.
2Your proxy asks the project about the request.
3The sign-in is older than /admin allows, so the project sends the browser to sign in again and says why.
4The person signs in again; anyone with an authenticator app types a code too.
5Back on /admin the sign-in is recent, and the project answers yes.
6Your proxy lets the request through to the admin page.
Good to know
Choose 15 minutes, an hour, 8 hours or a day. Pages that load data in the background, such as dashboards, stop working until the person reloads, so use it on admin paths.
Anyone who set up an authenticator app types a code when signing in again, whether or not the project requires one.
Tick "with a code from an authenticator app" and only a recent sign-in with a code opens the path. Before it saves, you see how many people it turns away; people without one are asked to set one up when the project lets them.
Without the code, a person who signs in through an outside provider is asked to sign in there again; how fresh that sign-in is, the provider decides. With it, they cannot open the path.
It is on every plan.
Prompt for your agent
Paste it into Claude, Cursor or another coding agent. It covers your code and the console setup. The prompt is in English.
Ask people to sign in again before /admin of my app behind the proxy, when their sign-in is more than 15 minutes old, and to type a code from an authenticator app.
Add a fresh sign-in condition with withCode to the rule for /admin, and tell me first how many people that affects.
The server’s issuer is <your project's issuer, on its Overview> and its discovery document is <issuer>/.well-known/openid-configuration.
If the FoxAuth administrative MCP is connected, use behind_proxy_app_update with rules[].conditions. Otherwise ask me to press the button for this in the console at https://auth.foxauth.dev/admin.
Use it on admin paths: a dashboard that loads data in the background stops until it is reloaded.
The browser did not allow copying. Select the text and copy it.
Under the hood: Forward auth · OpenID Connect max_age
A personReady on FoxAuth Cloud
People create their own account, or come by invitation
Opens in FoxAuth Cloud, in your project. You sign in first, or create a free account.
auth.acme-notes.app
AAcme Notes
Create an account
Email
Password
Create account
Already have an account? Sign in
A “Create an account” link on the sign-in page
A form for the address and a password
An email with a confirmation link
Turn on sign-up and the sign-in page offers “Create an account”, or invite people yourself from the Users page.
On your own server, this needs no setting switched on.
How it works, step by step
Person
FoxAuth
Inbox
1Creates an account
2Email with a link
3Opens the email
4Confirms
5Address proven
FoxAuth
Outside your control
A message
Happens inside one box
1The person clicks “Create an account” and types an address.
2FoxAuth sends a confirmation email.
3The person opens the email.
4They click the link.
5The address is marked verified: your app gets email_verified = true.
Good to know
Emails need a mail server (SMTP) set up.
An address is marked verified only when the person really confirmed it.
A forgotten password is reset by email, when the project allows it. The sign-in page then shows the link.
Prompt for your agent
Paste it into Claude, Cursor or another coding agent. It covers your code and the console setup. The prompt is in English.
Turn on self sign-up in my FoxAuth project and check that SMTP is set up.
The server’s issuer is <your project's issuer, on its Overview> and its discovery document is <issuer>/.well-known/openid-configuration.
If the FoxAuth administrative MCP is connected, use project_update (sign-up) and smtp_settings_get. Otherwise ask me to press the button for this in the console at https://auth.foxauth.dev/admin.
If SMTP is not set up, tell me instead of turning sign-up on.
The browser did not allow copying. Select the text and copy it.
Opens in FoxAuth Cloud, in your project. You sign in first, or create a free account.
auth.acme-notes.app
AAcme Notes
Sign in
Email
Password
Sign in
or
Continue with Google
The password page
Then a page asking for a six-digit code
On first use, a QR code to scan
After the password, the person types a six-digit code from an authenticator app. One switch asks it of everyone in the project.
On your own server, this needs no setting switched on.
How it works, step by step
Person
FoxAuth
Authenticatorapp
1Password
2Code needed
36 digits
4Types the code
5Signed in
FoxAuth
Outside your control
A message
Happens inside one box
1The person types their password.
2FoxAuth asks for the second-factor code.
3The authenticator app shows a code that changes every 30 seconds.
4The person types the code.
5Sign-in is complete, and your app gets its tokens.
Good to know
Any authenticator app works.
If someone loses their phone, an administrator removes the app on their user page.
Without the switch, people can still turn it on for themselves, and an application can require it on its own.
Prompt for your agent
Paste it into Claude, Cursor or another coding agent. It covers your code and the console setup. The prompt is in English.
Turn on the second factor (TOTP) in my FoxAuth project.
The server’s issuer is <your project's issuer, on its Overview> and its discovery document is <issuer>/.well-known/openid-configuration.
If the FoxAuth administrative MCP is connected, use project_update (second factor). Otherwise ask me to press the button for this in the console at https://auth.foxauth.dev/admin.
Tell me how many users have not set it up yet.
The browser did not allow copying. Select the text and copy it.
Under the hood: TOTP (RFC 6238)
A personReady on FoxAuth Cloud
Let people turn on two-step verification themselves
Opens in FoxAuth Cloud, in your project. You sign in first, or create a free account.
auth.acme-notes.app
AAcme Notes
Sign in
Email
Password
Sign in
or
Continue with Google
A Two-step verification page beside their connected apps
An email with a link, then a QR code
Afterwards, a page asking for the code at every password sign-in
Each person can add a code from an authenticator app to their own account, on their account page. From then on, every password sign-in asks them for it.
On your own server, this needs no setting switched on.
How it works, step by step
Person
FoxAuth
Inbox
Authenticatorapp
1Turns it on
2A link
3Opens it
46 digits
5Turned on
FoxAuth
Outside your control
A message
1On their account page, the person chooses Two-step verification.
2FoxAuth emails them a link that works only in that browser.
3The person opens the link and scans a QR code with the app.
4The app shows a code.
5The person types the code. Every later password sign-in asks for one.
Good to know
It is on by default. It needs password sign-in and a mail server.
If someone loses their phone, an administrator removes the app on their user page; a new one then needs a link we email them.
Signing in through Google or another provider does not ask for this code, so an application that requires one turns them away.
Prompt for your agent
Paste it into Claude, Cursor or another coding agent. It covers your code and the console setup. The prompt is in English.
Add a "Two-step verification" link to my app’s account settings that opens <your project's issuer, on its Overview>/account/security.
The server’s issuer is <your project's issuer, on its Overview> and its discovery document is <issuer>/.well-known/openid-configuration.
If the FoxAuth administrative MCP is connected, use project_update (totpSelfService). Otherwise ask me to press the button for this in the console at https://auth.foxauth.dev/admin.
Tell me how many people have set one up.
The browser did not allow copying. Select the text and copy it.
Opens in FoxAuth Cloud, in your project. You sign in first, or create a free account.
auth.acme-notes.app
AAcme Notes
Sign in
Email
Password
Sign in
or
Continue with Google
A code from an authenticator app after the password, once per sign-in
Without one, a page that offers to set one up and continue
A sign-in through a provider is told it cannot open this app
One application, such as billing, lets nobody in without a code from an authenticator app. The other applications of the project stay as they are.
On your own server, this needs no setting switched on.
How it works, step by step
Person
Yourapp
FoxAuth
Authenticatorapp
1Opens it
2Sign in
3Password and code
46 digits
5Signed in with a code
FoxAuth
Outside your control
A message
1The person opens the application and is sent to sign in.
2The application asks FoxAuth to sign the person in.
3FoxAuth asks for the password, then a code from the app. Someone without one can set it up right there.
4The app shows a code.
5FoxAuth tells the application the sign-in included a code.
Good to know
Turn it on in the application’s Settings, under "Require a code from an authenticator app". Before it saves, you see how many people it affects.
A code is asked once per sign-in, not every time the app opens.
Refresh tokens from sign-ins without a code stop working, so people sign in again with one.
People who sign in through a provider cannot open the app this way.
For an app behind your proxy, tick "with a code from an authenticator app" on the "Ask to sign in again" condition of a path instead.
Prompt for your agent
Paste it into Claude, Cursor or another coding agent. It covers your code and the console setup. The prompt is in English.
Make my billing application in FoxAuth require a code from an authenticator app, and tell me first how many people that affects.
The server’s issuer is <your project's issuer, on its Overview> and its discovery document is <issuer>/.well-known/openid-configuration.
If the FoxAuth administrative MCP is connected, use client_update (requireCode). Otherwise ask me to press the button for this in the console at https://auth.foxauth.dev/admin.
Make my app show a helpful page when it receives unmet_authentication_requirements.
The browser did not allow copying. Select the text and copy it.
Under the hood: OpenID Connect acr
An AI agentReady on FoxAuth Cloud
Ask for a code to connect an MCP server or API
1Your problem
PersonYourMCPserver
A stolen password connects an agent to your MCP server.→
Opens in FoxAuth Cloud, in your project. You sign in first, or create a free account.
auth.acme-notes.app
AAcme Notes
Sign in
Email
Password
Sign in
or
Continue with Google
A line on the sign-in page that names your MCP server
A code from an authenticator app after the password
Without one, a page that offers to set one up and continue
An agent connects to your MCP server only after its person signs in with a code from an authenticator app, and signs in again as often as you choose.
On your own server, this needs no setting switched on.
How it works, step by step
Person
AIagent
FoxAuth
YourMCPserver
1Connect
2Password and code
3Token for your server
4Calls a tool
FoxAuth
A message
Carries a token
1The agent asks FoxAuth for a token for your MCP server.
2FoxAuth asks the person for the password, then a code from the app, whatever the agent asked for.
3The token says the sign-in included a code.
4Your server, or your proxy, accepts only a token whose sign-in had a code.
Good to know
Turn it on in the Access tab of the API’s page, under "Require a code from an authenticator app". "Ask to sign in again every" asks people to reconnect at least that often. Before it saves, you see whom it affects.
Not every app asks people to sign in again on its own. In Claude Code they reconnect the server in /mcp. In claude.ai they get a Connect card. ChatGPT and Codex may only show an error. Try it with the apps your people use.
If an app does not carry on after the new sign-in, the person asks it to try again.
A connection made without a code stops at its next renewal, and its person signs in again with one.
Apps that act for no one, and sign-ins by assertion, cannot connect. People who sign in through a provider cannot give a code here.
Prompt for your agent
Paste it into Claude, Cursor or another coding agent. It covers your code and the console setup. The prompt is in English.
Make my MCP server in FoxAuth require a sign-in with a code from an authenticator app, and tell me first whom that affects.
The server’s issuer is <your project's issuer, on its Overview> and its discovery document is <issuer>/.well-known/openid-configuration.
If the FoxAuth administrative MCP is connected, use resource_update (requireCode, signInEveryMinutes). Otherwise ask me to press the button for this in the console at https://auth.foxauth.dev/admin.
If my MCP server checks its own tokens, make it refuse a token whose acr is not the multi-factor value FoxAuth names.
The browser did not allow copying. Select the text and copy it.
Under the hood: OAuth 2.0 Step Up Authentication Challenge (RFC 9470)
An AI agentReady on FoxAuth Cloud
Let only some people use one MCP tool
1Your problem
AIagentYourMCPserver
Anyone who may use your MCP server may call every tool.→
Opens in FoxAuth Cloud, in your project. You sign in first, or create a free account.
Nobody sees a new page
The agent says the tool was refused
One tool of your MCP server, such as delete_files, can be called only by the groups you choose, from the networks and in the hours you choose. Every other tool stays as open as before.
On your own server, this needs no setting switched on.
How it works, step by step
AIagent
Yourproxy
FoxAuth
YourMCPserver
1Calls delete_files
2Asks the project
3403: not for this tool
4Calls search_files
FoxAuth
Your reverse proxy
A message
A refusal
1The agent calls one tool of your MCP server and names it, as MCP 2026-07-28 asks.
2Your proxy asks the project to check the token and the tool.
3The person is not in the groups that may call delete_files, so the project says no. Their other tools still work.
4The same agent calls another tool, and your proxy lets it through.
Good to know
Set it on the Access tab of the API’s page: add its conditions under the tool. They add to the API’s own conditions and never replace them.
A tool condition stops an app that names the tool it calls honestly. A stolen token in an app that lies about the tool is stopped only by your MCP server checking the headers against the body, which MCP 2026-07-28 servers must do. To keep someone out of the whole API, use the API’s own conditions or its sign-in requirement.
Apps too old to say which tool they call are refused once a tool has conditions. Today that is many apps; the site’s client table says which.
A new or renamed tool on your server gets the “Any other tool” answer until you add it to the table.
Check access, at the bottom of the same tab, shows what the check would answer for a person, a tool, an address and a time.
Prompt for your agent
Paste it into Claude, Cursor or another coding agent. It covers your code and the console setup. The prompt is in English.
In FoxAuth, let only the Ops group call the delete_files tool of my MCP server, which my proxy checks. Keep every other tool as it is, and refuse apps too old to say which tool they call.
The server’s issuer is <your project's issuer, on its Overview> and its discovery document is <issuer>/.well-known/openid-configuration.
If the FoxAuth administrative MCP is connected, use resource_update (tools: a row with conditions, withoutMethod refuse). Otherwise ask me to press the button for this in the console at https://auth.foxauth.dev/admin.
Make sure my MCP server refuses a request whose Mcp-Method or Mcp-Name header differs from its body.
The browser did not allow copying. Select the text and copy it.
Under the hood: Forward auth · MCP 2026-07-28 request headers
Opens in FoxAuth Cloud, in your project. You sign in first, or create a free account.
auth.acme-notes.app
AAcme Notes
Sign in
Email
Password
Sign in
or
Continue with Google
From a listed address after three wrong passwords: "Password sign-in is not available from this network", what to do now, and a line to send you
With the right password at the first try: signed in, as before
The other ways to sign in stay on the page
Use FoxTrust’s list of addresses seen guessing passwords. An address on it gets three wrong passwords here, and then its password sign-ins are refused.
1Every hour your server downloads FoxTrust’s list of addresses seen guessing passwords, and checks its signature.
2An address on the list tries passwords against many accounts. Its first three wrong passwords are checked as usual.
3After three failures in an hour, the project refuses its next password without checking it, for as long as it keeps trying.
4Someone else on a listed address, such as a shared Wi-Fi, types their own password right the first time.
5They sign in as before, and your app gets its tokens.
Good to know
A super administrator turns the list on in Settings → Integrations, under Attack reporting. It needs attack reporting on, because the list is built from what servers report.
Each project starts at Count only. Nothing changes for anyone, and the Sign-in tab shows the numbers for 7 days. Choose Refuse password sign-in when they say it is safe.
A refused person sees a line to send you, with their address in it. Add that address under "Never check these networks", and they can sign in at once.
FoxTrust never learns who signs in. A list more than 3 hours old is not used, so nobody is refused because of it.
Only password sign-in is affected. Sign-in through an identity provider, password reset and sign-up are not. It is on every plan.
Prompt for your agent
Paste it into Claude, Cursor or another coding agent. It covers your code and the console setup. The prompt is in English.
Protect password sign-in in my FoxAuth project from addresses FoxTrust has seen guessing passwords.
Check that FoxTrust’s list is on and current, read the project’s numbers for the last 7 days, and tell me how many sign-ins from listed addresses had the right password. If I agree, set the project to refuse password sign-in from listed addresses.
The server’s issuer is <your project's issuer, on its Overview> and its discovery document is <issuer>/.well-known/openid-configuration.
If the FoxAuth administrative MCP is connected, use project_password_guessing_get, then project_update with passwordGuessing. Otherwise ask me to press the button for this in the console at https://auth.foxauth.dev/admin.
Turning the list on is an instance setting for a super administrator: attackerList.enabled, which needs attackReports.enabled.
The browser did not allow copying. Select the text and copy it.
Under the hood: Signed IP reputation list (FoxTrust)
Opens in FoxAuth Cloud, in your project. You sign in first, or create a free account.
auth.acme-notes.app
AAcme Notes
Sign in
Email
Password
Sign in
or
Continue with Google
The sign-in page, with your address in the address bar
The sign-in page lives at your project’s own address: a path such as /yourshop, or a subdomain such as yourshop on this server. A super administrator can instead put it on your own domain, such as login.yourshop.com, so to the person it is your site.
On your own server, this needs no setting switched on.
How it works, step by step
Person
Youraddress
FoxAuth
1Opens your address
2Reaches FoxAuth
3Finds the project
4Your sign-in page
FoxAuth
A message
Happens inside one box
1The person opens the project’s address: a path, a subdomain or a domain of your own.
2The address leads to FoxAuth. A domain of your own needs a DNS record that points to it.
3FoxAuth finds the project by its address. The project has its own issuer and its own signing keys.
4The person signs in on a page with your address.
Good to know
A project has exactly one of the three addresses: a path, a subdomain or a domain of its own.
An owner of the project’s team changes its path or subdomain, and only while the project holds no application, identity provider, provisioning connection or connected service.
After that, a super administrator changes it. A domain of your own is always a super administrator’s to set.
A domain of your own needs a DNS record and an https certificate.
Changing the address changes the issuer, so update it in your apps.
Prompt for your agent
Paste it into Claude, Cursor or another coding agent. It covers your code and the console setup. The prompt is in English.
Give my FoxAuth project the address name yourshop, as a path or a subdomain, and tell me what changes for my apps.
The server’s issuer is <your project's issuer, on its Overview> and its discovery document is <issuer>/.well-known/openid-configuration.
If the FoxAuth administrative MCP is connected, use project_address_change. Otherwise ask me to press the button for this in the console at https://auth.foxauth.dev/admin.
Remind me to update the issuer address in my apps.
The browser did not allow copying. Select the text and copy it.
1The person clicks “Sign out” in one of your apps.
2Your app sends the person to FoxAuth’s sign-out address.
3FoxAuth ends the person’s session.
4FoxAuth sends a sign-out notice, server to server, to every other app the person used.
5The person lands on your “signed out” page.
Good to know
Each app that should hear about it gives FoxAuth a sign-out notice address.
The notice goes from server to server, so it works even when the app’s tab is closed.
Sign-out notices are sent only while a super administrator has switched back-channel logout on in the server’s settings.
Check the logout token signature, iss, aud and the events claim before ending the session.
Prompt for your agent
Paste it into Claude, Cursor or another coding agent. It covers your code and the console setup. The prompt is in English.
Add sign-out through FoxAuth to my app: send the person to the end_session_endpoint from discovery with id_token_hint and post_logout_redirect_uri, and add a back-channel logout endpoint that validates the logout token and ends the local session.
The server’s issuer is <your project's issuer, on its Overview> and its discovery document is <issuer>/.well-known/openid-configuration.
If the FoxAuth administrative MCP is connected, use client_update with postLogoutRedirectUris and backchannelLogoutUri. Otherwise ask me to press the button for this in the console at https://auth.foxauth.dev/admin.
The browser did not allow copying. Select the text and copy it.
Under the hood: OIDC RP-Initiated Logout · OIDC Back-Channel Logout
Opens in FoxAuth Cloud, in your project. You sign in first, or create a free account.
auth.acme-notes.app
AAcme Notes
Sign in
Email
Password
Sign in
or
Continue with Google
Your primary colour on every sign-in page
Your logo and name on the consent page
The person’s language
Give your application its logo and its primary colour, and the sign-in pages wear them in English, Russian or Simplified Chinese.
On your own server, this needs no setting switched on.
How it works, step by step
Person
Yourapp
FoxAuth
1Clicks “Sign in”
2Sign-in, ui_locales=ru
3Logo, colour, language
4Your look, their language
FoxAuth
A message
The browser is sent on
Happens inside one box
1The person clicks “Sign in” in your app.
2Your app sends them to sign in, and may say which language it prefers.
3FoxAuth picks your colour, your logo for the consent page, and the person’s language.
4The person signs in on a page that looks like your product.
Good to know
The logo is an image you upload: PNG, JPEG or WebP, up to 64 KiB.
They show for an application of your own organisation, not on a device sign-in, and not when every callback address is local.
FoxAuth shifts the colour to the nearest readable shade, in light and in dark mode.
The language is the person’s own choice first, then your app’s ui_locales, then the browser’s. The console and administrator emails stay in English.
Prompt for your agent
Paste it into Claude, Cursor or another coding agent. It covers your code and the console setup. The prompt is in English.
Give my FoxAuth application its logo and primary colour, and pass ui_locales from my app’s current language when it sends people to sign in.
The server’s issuer is <your project's issuer, on its Overview> and its discovery document is <issuer>/.well-known/openid-configuration.
If the FoxAuth administrative MCP is connected, use client_update with logo and primaryColor. Otherwise ask me to press the button for this in the console at https://auth.foxauth.dev/admin.
The browser did not allow copying. Select the text and copy it.
Under the hood: OpenID Connect ui_locales · logo · primary colour
A personReady on FoxAuth Cloud
People see and remove the apps that can reach their account
Opens in FoxAuth Cloud, in your project. You sign in first, or create a free account.
A list of the apps that can reach their account
A button to remove each one
Every project has an account page that lists the apps holding access to the signed-in person, and they can remove any of them.
On your own server, this needs no setting switched on.
How it works, step by step
Person
FoxAuth
1Opens /account/apps
2Apps with access
3Removes one
4Access ended
FoxAuth
A message
Happens inside one box
1The person opens the account page of your project.
2FoxAuth lists the apps that can reach their account.
3The person removes an app.
4FoxAuth ends that app’s access. The next time the app asks, it is refused.
Good to know
There is nothing to switch on.
The page lives at your project’s own address, at /account/apps.
Link to it from your app’s account settings.
Prompt for your agent
Paste it into Claude, Cursor or another coding agent. It covers your code and the console setup. The prompt is in English.
Add a “Connected apps” link to my app’s account settings that opens <your project's issuer, on its Overview>/account/apps.
The server’s issuer is <your project's issuer, on its Overview> and its discovery document is <issuer>/.well-known/openid-configuration.
Ask me to press the button for this in the console at https://auth.foxauth.dev/admin.
The browser did not allow copying. Select the text and copy it.
Under the hood: Grant management for end users
A personReady on FoxAuth Cloud
People see their own sign-ins and sign out everywhere
1Your problem
Person
A person who thinks someone else uses their account has nowhere to look.→
2With FoxAuth
PersonFoxAuth
People check their sign-ins and shut out whoever wasn’t them.→
Opens in FoxAuth Cloud, in your project. You sign in first, or create a free account.
Their last ten sign-ins, with app, time, method, browser and country
A button to sign out everywhere
The account page lists a person’s last ten sign-ins, without the address. If one wasn’t them, they sign out of every app at once and get a link to set a new password.
On your own server, this needs no setting switched on.
How it works, step by step
Person
FoxAuth
1Opens Recent sign-ins
2Their last ten sign-ins
3Signs out everywhere
4Every way in ended
FoxAuth
A message
Happens inside one box
1The person opens Recent sign-ins on the account page and signs in again if their sign-in is older than 15 minutes.
2FoxAuth lists each sign-in: the app, when, how, the browser and the country.
3One of them wasn’t them, so they sign out everywhere.
4FoxAuth ends every session and token of the account and mails a link to set a new password.
Good to know
There is nothing to switch on.
The page never shows the address a sign-in came from.
Signing out everywhere doesn’t lock the account, and you see it under the person’s Changes.
Prompt for your agent
Paste it into Claude, Cursor or another coding agent. It covers your code and the console setup. The prompt is in English.
Add a “Recent sign-ins” link to my app’s account settings that opens <your project's issuer, on its Overview>/account/sign-ins.
The server’s issuer is <your project's issuer, on its Overview> and its discovery document is <issuer>/.well-known/openid-configuration.
Ask me to press the button for this in the console at https://auth.foxauth.dev/admin.
The browser did not allow copying. Select the text and copy it.
Opens in FoxAuth Cloud, in your project. You sign in first, or create a free account.
Nobody sees a screen: this is between your app and your API
With DPoP, each token works only together with a fresh proof signed by a key that never leaves your app, so a copied token on its own is refused.
On your own server, switch on in Settings: dpop.enabled
How it works, step by step
Yourapp
FoxAuth
YourAPI
Someonewithacopy
1Token + key proof
2Token bound to the key
3Token + new proof
4Copied token
FoxAuth
Outside your control
A message
Carries a token
A refusal
1Your app asks for a token and signs a proof with its own key.
2FoxAuth binds the token to that key.
3Each call carries the token and a new proof.
4Someone with a copy of the token has no key, so your API refuses it.
Good to know
Your API checks the DPoP proof along with the token.
Client certificates (mTLS) do the same job, on your own server only.
Prompt for your agent
Paste it into Claude, Cursor or another coding agent. It covers your code and the console setup. The prompt is in English.
Make my app use DPoP with FoxAuth: generate a key pair kept in memory, send a DPoP proof with every token request and every API call, and make my API verify the proof (htm, htu, ath, jti) as well as the token’s cnf.jkt.
The server’s issuer is <your project's issuer, on its Overview> and its discovery document is <issuer>/.well-known/openid-configuration.
If the FoxAuth administrative MCP is connected, use client_update with dpopBoundAccessTokens true. Otherwise ask me to press the button for this in the console at https://auth.foxauth.dev/admin.
The browser did not allow copying. Select the text and copy it.
Under the hood: DPoP (RFC 9449) · mTLS certificate-bound tokens (RFC 8705)
EnterpriseReady on FoxAuth Cloud
Company sign-in
1Your problem
EmployeeYourapp
Your app keeps passwords company IT cannot close.→
3FoxAuth sends the employee to their company’s provider.
4The company’s provider confirms who it is.
5Your app gets ordinary tokens.
Good to know
What you ask the company’s IT department for: the provider address, an ID and a secret.
It usually comes with the next one: the company also wants its directory to create and remove people.
Prompt for your agent
Paste it into Claude, Cursor or another coding agent. It covers your code and the console setup. The prompt is in English.
Connect company sign-in through the customer’s OpenID provider (Okta) to my FoxAuth project. Tell me what to ask the customer’s IT department for.
The server’s issuer is <your project's issuer, on its Overview> and its discovery document is <issuer>/.well-known/openid-configuration.
If the FoxAuth administrative MCP is connected, use federation_provider_create with kind oidc. Otherwise ask me to press the button for this in the console at https://auth.foxauth.dev/admin.
The browser did not allow copying. Select the text and copy it.
A SCIM connection lets the company’s directory create, change and deactivate people in your project, while your apps keep asking FoxAuth who may sign in.
1Someone joins the company. The directory creates them in FoxAuth.
2They move to another department. The directory updates the record.
3They leave. The directory deactivates them.
4Later they try to sign in to one of your apps.
5FoxAuth refuses. Nothing is sent to your app: it simply never gets a token for them.
Good to know
You give the company’s IT a SCIM address and a token. They work with Entra ID or Okta.
A person from the directory is read-only in the console, except the local lock.
It usually comes with company sign-in, and works with a sign-in provider you have already added.
Prompt for your agent
Paste it into Claude, Cursor or another coding agent. It covers your code and the console setup. The prompt is in English.
Create a SCIM connection for Entra ID in my FoxAuth project, and tell me what the customer’s IT department enters on their side.
The server’s issuer is <your project's issuer, on its Overview> and its discovery document is <issuer>/.well-known/openid-configuration.
If the FoxAuth administrative MCP is connected, use provisioning_connection_create. Otherwise ask me to press the button for this in the console at https://auth.foxauth.dev/admin.
The browser did not allow copying. Select the text and copy it.
Opens in FoxAuth Cloud, in your project. You sign in first, or create a free account.
Nobody sees a screen: the groups arrive in the token
Put people into project groups, and your app gets them in the token’s groups field and decides what to show.
On your own server, this needs no setting switched on.
How it works, step by step
Person
Yourapp
FoxAuth
1Signs in
2Anna is in Finance
3groups: Finance
4Shows the right part
FoxAuth
A message
Carries a token
Happens inside one box
1Anna signs in to your app.
2In the project, Anna is a member of the Finance group.
3Your app gets her groups in the token.
4Your app opens the finance section for Anna.
Good to know
The company’s directory can send the groups too, through SCIM.
Prompt for your agent
Paste it into Claude, Cursor or another coding agent. It covers your code and the console setup. The prompt is in English.
Create a Finance group in my FoxAuth project, and show me how to read the groups field in my app.
The server’s issuer is <your project's issuer, on its Overview> and its discovery document is <issuer>/.well-known/openid-configuration.
If the FoxAuth administrative MCP is connected, use project_group_create. Otherwise ask me to press the button for this in the console at https://auth.foxauth.dev/admin.
The browser did not allow copying. Select the text and copy it.
Opens in FoxAuth Cloud, in your project. You sign in first, or create a free account.
The person is signed out of every app, with no page to see
Deactivate the person in FoxAuth, or let the company’s provider sign them out everywhere by itself.
On your own server, this needs no setting switched on.
How it works, step by step
CompanyIT
OktaorEntraID
FoxAuth
Yourapps
1Deactivates
2Sign out everywhere
3Sessions ended
4Sign-out notice
FoxAuth
Outside your control
A message
Happens inside one box
1The IT department deactivates the employee on their side.
2The company’s provider tells FoxAuth to sign the person out.
3FoxAuth ends the sessions and revokes the tokens.
4Your apps receive a sign-out notice.
Good to know
You can do it by hand: Users, the person, Deactivate.
Their activity stays for 90 days after you deactivate them, so you can still see what they used.
The company’s provider can do it for you only after you add it as a sign-in provider and a super administrator switches on the signals it sends, in the server’s settings.
Prompt for your agent
Paste it into Claude, Cursor or another coding agent. It covers your code and the console setup. The prompt is in English.
Deactivate the user anna@acme.com in my FoxAuth project and end all of their sessions.
The server’s issuer is <your project's issuer, on its Overview> and its discovery document is <issuer>/.well-known/openid-configuration.
If the FoxAuth administrative MCP is connected, use project_user_update and project_user_sign_out. Otherwise ask me to press the button for this in the console at https://auth.foxauth.dev/admin.
The browser did not allow copying. Select the text and copy it.
Under the hood: Okta Universal Logout · OIDC Back-Channel Logout
1The agent asks the company’s provider for access to your app.
2The provider issues an assertion (an ID-JAG).
3The agent presents the assertion to FoxAuth.
4FoxAuth issues a token, with no consent screen.
5The agent calls your API.
Good to know
Trust is switched on at the sign-in provider: “Accept assertions”.
These tokens come with no refresh token.
Assertions never reach the administrative MCP or SCIM.
Prompt for your agent
Paste it into Claude, Cursor or another coding agent. It covers your code and the console setup. The prompt is in English.
Turn on accepting ID-JAG assertions from the company sign-in provider in my FoxAuth project, and explain how an agent trades an assertion for a token.
The server’s issuer is <your project's issuer, on its Overview> and its discovery document is <issuer>/.well-known/openid-configuration.
If the FoxAuth administrative MCP is connected, use federation_provider_update. Otherwise ask me to press the button for this in the console at https://auth.foxauth.dev/admin.
The browser did not allow copying. Select the text and copy it.
Under the hood: ID-JAG · OAuth 2.0 Token Exchange (RFC 8693) · JWT bearer
1Your app asks for a token for one payment, described in detail.
2FoxAuth shows the person the payment itself.
3The person approves it.
4FoxAuth issues a token that carries this payment and nothing more.
5Your payment API reads the details from the token and carries them out.
Good to know
Each kind of action is declared once in the server’s settings, with the label the consent page shows.
The details go only into a token for one declared API.
It works with sign-in codes and refresh tokens, not with the other flows.
Prompt for your agent
Paste it into Claude, Cursor or another coding agent. It covers your code and the console setup. The prompt is in English.
Make my app request a payment with authorization_details of type https://scheme.example/payment (actions: initiate, amount, currency, creditor account) and resource set to my payment API, and make the API read authorization_details from the token.
The server’s issuer is <your project's issuer, on its Overview> and its discovery document is <issuer>/.well-known/openid-configuration.
Ask me to press the button for this in the console at https://auth.foxauth.dev/admin.
The browser did not allow copying. Select the text and copy it.
Under the hood: Rich Authorization Requests (RFC 9396) · authorization_details
It is a setting for the whole server, switched on by a super administrator.
Prompt for your agent
Paste it into Claude, Cursor or another coding agent. It covers your code and the console setup. The prompt is in English.
Explain how to switch CIBA on in FoxAuth, and how a call centre system sends an approval request.
The server’s issuer is <your project's issuer, on its Overview> and its discovery document is <issuer>/.well-known/openid-configuration.
Ask me to press the button for this in the console at https://auth.foxauth.dev/admin.
The browser did not allow copying. Select the text and copy it.
2FoxAuth lists the applications that would stop working.
3You switch the profile on.
4The rules now apply to every application.
Good to know
Run the readiness check first: it names the applications that would stop working.
Each token is bound to the application’s key with DPoP, so a stolen token is useless.
PKCE is required on every sign-in, and only applications registered in advance may sign in.
Signatures use PS256, ES256 or EdDSA.
A separate setting, FAPI behaviours, also makes an application’s signed assertion name this server as its only audience.
A second factor on request works for people with a password and an authenticator app, not for people who sign in through a provider; the readiness check lists projects where nobody new could give one.
It is a setting for the whole server.
Prompt for your agent
Paste it into Claude, Cursor or another coding agent. It covers your code and the console setup. The prompt is in English.
Check whether my FoxAuth server is ready for the IPSIE SL1 profile, and list what needs fixing.
The server’s issuer is <your project's issuer, on its Overview> and its discovery document is <issuer>/.well-known/openid-configuration.
If the FoxAuth administrative MCP is connected, use settings_ipsie_profile_readiness_get. Otherwise ask me to press the button for this in the console at https://auth.foxauth.dev/admin.
The browser did not allow copying. Select the text and copy it.
Under the hood: IPSIE SL1 · DPoP (RFC 9449) · PKCE
Opens in FoxAuth Cloud, in your project. You sign in first, or create a free account.
The trail in the console: who changed what, and when
Teams own projects, membership is the only thing that grants access, and every change goes into a trail that nobody can edit.
On your own server, this needs no setting switched on.
How it works, step by step
Team
Project
Audittrail
1Owns
2Members work
3Every change
4Cannot be edited
FoxAuth
A message
Happens inside one box
1The Payments team owns its projects.
2Only the team’s members can reach the project.
3Every change is written to the trail.
4Nobody can change or delete an entry.
Good to know
There are no roles: membership of a team grants access.
The trail is under Audit, in the menu.
Prompt for your agent
Paste it into Claude, Cursor or another coding agent. It covers your code and the console setup. The prompt is in English.
Create a Payments team in FoxAuth and show me the latest entries in the audit trail.
The server’s issuer is <your project's issuer, on its Overview> and its discovery document is <issuer>/.well-known/openid-configuration.
If the FoxAuth administrative MCP is connected, use team_create and audit_list. Otherwise ask me to press the button for this in the console at https://auth.foxauth.dev/admin.
The browser did not allow copying. Select the text and copy it.
This needs a super administrator, and on FoxAuth Cloud nobody is one. On your own server, a super administrator sets it up.
auth.acme-notes.app
AAcme Notes
Sign in
Email
Password
Sign in
or
Continue with Google
The administrators’ sign-in page, then back to the tool
Register the tool as an application in the administrators’ project, and the groups field names the administrator’s teams.
How it works, step by step
Administrator
Internaltool
FoxAuth
1Opens it
2Administrator sign-in
3groups: their teams
4Lets the right teams in
FoxAuth
A message
The browser is sent on
Carries a token
Happens inside one box
1An administrator opens the internal tool.
2The tool sends them to the administrators’ sign-in.
3The tool gets the administrator’s teams.
4The tool opens itself to the teams it trusts.
Good to know
A super administrator registers it, and only in the console.
Sign-in only: such applications get no tokens for an API.
Prompt for your agent
Paste it into Claude, Cursor or another coding agent. It covers your code and the console setup. The prompt is in English.
Explain how a super administrator registers an internal tool as an application in the administrators’ project, in the console at https://auth.foxauth.dev/admin. An agent cannot do this: it is withheld from agents.
The browser did not allow copying. Select the text and copy it.
Under the hood: OpenID Connect · groups claim
EnterpriseOn your own server
Your administrators sign in to the console with company SSO
This needs a super administrator, and on FoxAuth Cloud nobody is one. On your own server, a super administrator sets it up.
auth.acme-notes.app
AAcme Notes
Sign in
Continue with Acme Corp
or
Email
Password
The console’s sign-in page with a button for the company
Then the company’s own sign-in page, and back
Add the company’s provider to the administrators’ project, and the console’s sign-in page offers it while FoxAuth makes sure the console can never lock itself.
1An administrator opens the console and picks the company provider.
2FoxAuth sends them to the company’s provider.
3The provider confirms who it is.
4FoxAuth links them to their existing administrator account.
5The administrator is in the console.
Good to know
Only a super administrator configures it.
A new provider admits only people who already have an administrator account. Linking the first time needs their password.
Passwords can be switched off only while a super administrator can still come in through the provider.
Prompt for your agent
Paste it into Claude, Cursor or another coding agent. It covers your code and the console setup. The prompt is in English.
Explain how a super administrator adds the company’s sign-in provider to the administrators’ project, in the console at https://auth.foxauth.dev/admin, so administrators can sign in with company SSO.
The browser did not allow copying. Select the text and copy it.
Under the hood: OpenID Connect · federation into the console
Nothing fits? Configure everything yourself
Every application can be set up by hand. The console’s full form names every field the way the protocol does, with nothing preset.