Skip to content

docs: clarify auth vs adminAuth for wallet gateway configuration#804

Open
Ash-code183 wants to merge 1 commit into
canton-network:mainfrom
Ash-code183:hermes/docs/788-wallet-gateway-auth-clarity
Open

docs: clarify auth vs adminAuth for wallet gateway configuration#804
Ash-code183 wants to merge 1 commit into
canton-network:mainfrom
Ash-code183:hermes/docs/788-wallet-gateway-auth-clarity

Conversation

@Ash-code183

Copy link
Copy Markdown
  • Add explicit mapping: auth (user-facing UI) should use authorization_code
  • Clarify that adminAuth (backend) should use client_credentials
  • Replace general recommendations with auth/adminAuth context table
  • Add IMPORTANT callout explaining the UI vs backend distinction

Fixes #788

- Add explicit mapping: auth (user-facing UI) should use authorization_code
- Clarify that adminAuth (backend) should use client_credentials
- Replace general recommendations with auth/adminAuth context table
- Add IMPORTANT callout explaining the UI vs backend distinction

Fixes canton-network#788
@Jatinp26 Jatinp26 self-requested a review June 18, 2026 12:49
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.

wallet gateway configuration is unclear

2 participants