For querying users where some data resides at Fusion Auth DB & rest at Hasura side.
Changes
GET /admin/user/:userId
Use the existing devised generic approach; we'll add a new variable in env file JSON against the application ID with a new hasura Query, which will query & add a new fields in the response of this API. E.g.
Request body:
The above is existing GET API. We can pass the request payload as JSON (not sure if it is fine or not). Or, shall we add a new API (like POST /admin/user/:userId/getDetails) with request/response payload/body as mentioned above?
Description
For querying users where some data resides at Fusion Auth DB & rest at Hasura side.
Changes
GET /admin/user/:userId Use the existing devised generic approach; we'll add a new variable in env file JSON against the application ID with a new hasura Query, which will query & add a new fields in the response of this API. E.g. Request body:
Response body:
Open Questions: