You are working on the hyperswitch repository (Rust payment processing system).…
- User
You are working on the hyperswitch repository (Rust payment processing system).
REPOSITORY SETUP:
- Repository: juspay/hyperswitch
- Working directory: ./repos/hyperswitch_pool_5 (already cloned)
- Base commit: b04ccafe48394fad86bf072b2e3a74626cc26550
- Task ID: juspay__hyperswitch-7931
- Version: v1.114.0
TASK DESCRIPTION: Bug: Modify User-related Redis Operations to Use Global Tenant Prefix
Currently, user-related data in Redis (such as SSO IDs, TOTP codes, email token blacklists, lineage_context etc.) is using tenant-specific prefixes like
public:orpublic_v2:. This causes issues when users use different versions or environments (v1, v2), leading to inconsistency in fetching and setting Redis keys.The correct prefix for all global user-related data should be
global:.Affected Areas
- Blacklisting
- Two-factor Authentication (TOTP, Recovery Codes)
- SSO ID storage
- OpenID Connect (OIDC) token handling
- Role Info Caching
- Lineage Context
DETAILED CONTEXT & HINTS:
Type of Change
- Bugfix
- New feature
- Enhancement
- Refactoring
- Dependency updates
- Documentation
- CI/CD
Description
This PR updates all user-related Redis operations to consistently use the global Redis key prefix (
global:) instead of environment-specific prefixes likepublic:(V1) orpublic_v2:(V2).Previously, different deployments used different prefixes, which caused inconsistencies especially during login, logout, switch, and caching flows.
Changes Introduced:
- Updated Redis connection fetchers for all user modules (lineage context, SSO, blacklist, etc.) to use a global Redis connection.
Affected functions:
utils/user.rsset_sso_id_in_redisget_sso_id_from_redis
utils/user/two_factor_auth.rscheck_totp_in_redischeck_recovery_code_in_redisinsert_totp_in_redisinsert_totp_secret_in_redisget_totp_secret_from_redisdelete_totp_secret_from_redisinsert_recovery_code_in_redisdelete_totp_from_redisdelete_recovery_code_from_redisinsert_totp_attempts_in_redisget_totp_attempts_from_redisinsert_recovery_code_attempts_in_redisget_recovery_code_attempts_from_redisdelete_totp_attempts_from_redisdelete_recovery_code_attempts_from_redis
services/authorization.rsget_role_info_from_cacheset_role_info_in_cache
services/openidconnect.rsget_authorization_urlget_nonce_from_redis
services/user.rsinsert_user_in_blacklistinsert_role_in_blacklistinvalidate_role_cachecheck_user_in_blacklistcheck_role_in_blacklistinsert_email_token_in_blacklistcheck_email_token_in_blacklist
Additional Changes
- This PR modifies the API contract
- This PR modifies the database schema
- This PR modifies application configuration/environment variables
Motivation and Context
- It helps in storing the redis keys which are common to both v1 and v2 deployments under a common prefix, so it can be used irrespective of the version of the deployment.
How did you test it?
Used the dashboard and then signed out. As it is evident in the screenshot, blacklist functions, and lineage context now use
global:prefix while setting the key in redis.We need to check the redis-cli and verify that the user-related keys have the
globalprefix, instead of deployment specific keys likepublicandpublic_v2.Checklist
- I formatted the code
cargo +nightly fmt --all - I addressed lints thrown by
cargo clippy - I reviewed the submitted code
- I added unit tests for my changes where possible
CRITICAL INSTRUCTIONS - WORK FAST AND EFFICIENTLY:
-
Create DENSE, ACTION-FOCUSED todos IMMEDIATELY
- Make todos specific and actionable
- Focus on HIGH-IMPACT actions only
- 5-8 todos maximum - be surgical, not exhaustive
-
Execute aggressively:
- Use bash commands to search efficiently
- Read multiple related files in quick succession
- Make ALL related changes in one edit
- Skip unnecessary exploration
-
File operations:
- All repo files: './repos/hyperswitch_pool_5/'
- Use targeted edits over whole file rewrites
-
NO TESTING UNLESS CRITICAL:
- Focus on making the actual code changes
- Only test if explicitly required
-
Maximize information density:
- Each turn should accomplish significant work
- Batch file reads when examining related code
- Use search commands to locate code quickly
EFFICIENCY IS CRITICAL. Make substantial progress every turn.
Assistant
I'll help you implement the changes to modify user-related Redis operations to use the global tenant prefix. Let me start by creating a plan and then execute the necessary changes.
First, let me explore the repository structure to understand where the affected files are located.
Assistant
Let me first explore the repository structure to locate the files mentioned in the task description.
Assistant
Now let me look more specifically at the files mentioned in the task description to understand the current Redis key prefix usage:
Assistant
Let me check the utils/user.rs file which contains the SSO ID functions:
Assistant
Now let me check the two_factor_auth.rs file to see the TOTP-related Redis operations:
Assistant
Now let me check the authorization.rs file for role info caching:
Assistant
Let me check the openidconnect.rs file:
Assistant
Now let me check the user.rs file in the services module for blacklist operations:
Assistant
Let me check if there's a user.rs file in the services directory:
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.
Identical first prompt
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →