Tests and demo routes for fastapi_auth_jwt.
The tests and routes are almost identical to those in auth_jwt_demo, and the JWT validators used are those from auth_jwt_demo.
auto_awesome What this module does
AI-generated from the code · Odoo 16.0Adds a demo/test FastAPI endpoint type called "Auth JWT Demo Endpoint" to Odoo, exposing sample web routes that show who is authenticated via JWT tokens.
This is a technical demo module. It extends the fastapi.endpoint model with a new application option named "Auth JWT Demo Endpoint" (technical value auth_jwt_demo), so administrators can create an endpoint record of that type and attach it to a user.
The module ships a demo endpoint record named "Auth JWT Fastapi Demo Endpoint" with root path /fastapi_auth_jwt_demo, linked to the demo application user.
When an endpoint uses this application, the module registers a set of sample routes:
- /whoami and /cookie/whoami and /keycloak/whoami return the authenticated partner's name, email and user id, using different JWT validators (demo, demo_cookie, demo_keycloak).
- /whoami-public-or-jwt, /cookie/whoami-public-or-jwt and /keycloak/whoami-public-or-jwt work both with and without a valid token: if a token is present the partner details are returned, otherwise only the user id is returned.
There are no menus, no business rules, no scheduled jobs and no changes to standard Odoo screens. The module only touches the fastapi.endpoint model and provides test routes for the JWT authentication framework.
Depends on
Models and fields (1)
- fastapi.endpoint · extends an existing model
Text generated by AI (DeepSeek) from reading the Odoo 16.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 16.0
Confirmed on 2026-11-03 in branch 16.0 of OCA/rest-framework.
terminal Installation and usage
No verified informationInstallation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.