fix: Update tenant selector template to work with dictionary objects #652
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Add logging for request context (URL, host, scheme) - Log each step of redirect URI generation - Add GOOGLE_OAUTH_REDIRECT_URI to .env.example with examples - Will help diagnose redirect_uri_mismatch errors
The template was expecting tuples (tenant_id, tenant_name) but the OAuth
callback passes dictionary objects with keys: tenant_id, name, subdomain.
Changed the template iteration from:
{% for tenant_id, tenant_name in tenants %}
To:
{% for tenant in tenants %}
And updated field access to use dot notation (tenant.tenant_id, tenant.name).
This fixes the 500 error users encountered after successful OAuth authentication
when reaching the tenant selection page.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
This was referenced Oct 28, 2025
danf-newton
pushed a commit
to Newton-Research-Inc/salesagent
that referenced
this pull request
Nov 24, 2025
…dcontextprotocol#652) * debug: Add detailed OAuth redirect URI logging and env var documentation - Add logging for request context (URL, host, scheme) - Log each step of redirect URI generation - Add GOOGLE_OAUTH_REDIRECT_URI to .env.example with examples - Will help diagnose redirect_uri_mismatch errors * fix: Update tenant selector template to work with dictionary objects The template was expecting tuples (tenant_id, tenant_name) but the OAuth callback passes dictionary objects with keys: tenant_id, name, subdomain. Changed the template iteration from: {% for tenant_id, tenant_name in tenants %} To: {% for tenant in tenants %} And updated field access to use dot notation (tenant.tenant_id, tenant.name). This fixes the 500 error users encountered after successful OAuth authentication when reaching the tenant selection page. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> --------- Co-authored-by: Claude <noreply@anthropic.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixes 500 error on tenant selection page after successful OAuth authentication.
Problem
The
choose_tenant.htmltemplate was trying to unpack tuples:But the OAuth callback was passing a list of dictionary objects:
This caused a 500 error when users successfully authenticated and reached the tenant selection page.
Solution
Updated the template to iterate over dictionaries directly:
Testing
auth.pyRelated
🤖 Generated with Claude Code