Issue with Redis Database ID Not Being Applied During Jedis Pool Initialization in Choreo Connect

[Samitha-001]

Description

Hi Team,

The Redis databaseID configuration for burst control and backend throttling in Choreo Connect is not being applied correctly. The issue occurs because the JedisPool constructors used in the ThrottlerInitializer class do not support specifying the database ID when no username or password is provided. As a result, the system always defaults to Redis database 0, even if a different redisDatabaseID is configured.

Steps to Reproduce

Test Setup

• Choreo Connect Router 1 node
• Choreo Connect Enforcer 1 node
• Choreo Connect Adapter 1 node
• WSO2 AM 4.0.0 1 node
• Redis Cache server 1 node

Configure Choreo Connect to use a Redis instance for distributed throttling with a custom redisDatabaseID, as shown below:

[enforcer.throttling.localThrottler.distributedCounter]
enabled = true
redisHost = "redis"
redisPort = 6379
redisUser = ""
redisPass = ""
redisDatabaseID = 1

Version

1.0.0

Environment Details (with versions)

No response

Relevant Log Output

No response

Related Issues

No response

Suggested Labels

No response