Skip to content

Conversation

@pmalouin
Copy link
Contributor

No description provided.

RESOURCE_SERVER_CLIENT_ID="<your-resource-server-client-id>"
RESOURCE_SERVER_CLIENT_SECRET="<your-resource-server-client-secret>"
# on behalf of the user within your Langgraph API. Only needed for Langgraph example.
CUSTOM_API_CLIENT_ID="<your-custom-api-client-id>"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if ok w/ you, can we stick w/ AUTH0_CUSTOM_API_CLIENT_{X} convention?

We started that recently, and i like to keep prefix the "AUTH0_" prefix if we can, and naming has been consistent in the other samples/docs (until we name it otherwise 😛 )

https://github.com/search?q=repo%3Aauth0%2Fdocs-v2%20AUTH0_CUSTOM_API&type=code
https://github.com/search?q=repo%3Aauth0-samples%2Fauth0-ai-samples%20AUTH0_CUSTOM_API&type=code

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

great suggestion! fixed ✔️

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ty 🙇

@priley86
Copy link
Contributor

priley86 commented Nov 4, 2025

  • verified both examples to work w/ my GenAI tenant locally
  • discussed upcoming changes in auth0 docs-v2 repo (captured in: https://auth0team.atlassian.net/browse/AIDX-240)
  • known limitation about loss of message history in Hono + React SPA example after step up flow is acceptable to the business as of now (and could be improved in future w/ popup flow vs redirect flow)

priley86
priley86 previously approved these changes Nov 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants