Proxy Auth Tokens
Use Proxy Auth Tokens to prevent unauthorized clients from triggering your web endpoints.
The public endpoint can be hit by any client over the Internet.
The private endpoint cannot.
Authorization is demonstrated via a Proxy Auth Token. You can create a Proxy Auth Token for your workspace here.
In requests to the web endpoint, clients supply the Token ID and Token Secret in the Modal-Key and Modal-Secret HTTP headers.
Proxy authorization can be added to web endpoints created by the fastapi_endpoint, asgi_app, wsgi_app, or web_server decorators,
which are otherwise publicly available.
Everyone within the workspace of the web endpoint can manage its Proxy Auth Tokens.
Restricting tokens to specific Environments
On workspaces with RBAC enabled, tokens can be scoped to specific Environments, restricting which web endpoints they are valid for. See Proxy auth tokens for web endpoints in the RBAC guide for more.