fix: forwarda X-Evo-Tenant-Id ao buscar credenciais OAuth no CRM#27
Merged
Merged
Conversation
Ao conectar Google Calendar/GitHub/etc, o processor buscava as credenciais OAuth no CRM só com X-Service-Token, SEM o tenant → o CRM resolvia a config global (vazia) → 500 'credentials not configured', mesmo com a credencial BYO da marca existindo. As rotas OAuth agora leem o tenant do request via runtime_context.current_context_id(request) e passam get_<provider>_credentials( tenant_id=cid); o service anexa X-Evo-Tenant-Id junto do X-Service-Token quando há tenant (no-op standalone). 14 providers.
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
There was a problem hiding this comment.
Sorry @DavidsonGomes, you have reached your weekly rate limit of 500000 diff characters.
Please try again later or upgrade to continue using Sourcery
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Conectar Google Calendar/GitHub/etc dava 500 'credentials not configured' mesmo com a credencial BYO da marca configurada: o processor buscava as credenciais no CRM so com X-Service-Token, sem o tenant, entao o CRM resolvia a config global (vazia). As rotas OAuth leem o tenant do request via runtime_context.current_context_id e passam tenant_id p/ get__credentials, que anexa X-Evo-Tenant-Id quando presente (no-op standalone). 14 providers.