Sandeep Kumar

refactor(authentication): modify auth for profiles and mca routes to `ApiKeyAuthWithMerchantIdFromRoute`

1

## Type of Change - [ ] Bugfix - [ ] New feature - [ ] Enhancement - [x] Refactoring - [ ] Dependency updates - [ ] Documentation -...

### Description: Currently, the following routes use `AdminApiAuthWithMerchantIdFromRoute` for authentication: - Profile Create, Retrieve, Update - Merchant Connector Account Create, List, Retrieve, Update This has to be updated to a...

Description: Currently, the following routes use AdminApiAuthWithMerchantIdFromRoute for authentication: Profile Create, Retrieve, Update Merchant Connector Account Create, List, Retrieve, Update This has to be updated to a more appropriate auth...

Development to modify the Users structure to all product types

1

Based on discussions, development needs to be done accordingly to extend the users to all product types.

Need to discuss backfilling: - `id` column from `org_id` column in organization table on sandbox - `id` column from `org_id` column in organization table on production - `id` column from...

Need to update the API Collection present on the website, to use API Key instead of AdminAPI Key. cc: @gorakhnathy7

Need to update the Postman Collection for all the connectors, to use API Key instead of AdminAPI Key, to avoid throwing errors on Jenkins Pipeline.

feat(user): use global redis key prefix for user lineage context

1

## Type of Change - [ ] Bugfix - [x] New feature - [ ] Enhancement - [ ] Refactoring - [ ] Dependency updates - [ ] Documentation -...

Currently, the lineage context is cached in Redis using tenant-specific key prefixes (public_, public_v2_). This causes inconsistencies across V1 and V2 environments — especially during login/logout flows — as lineage...

Currently, when a new organization is created during sign-up, the system automatically creates an Orchestration V1 merchant account. This happens even if the merchant has no intention of using the...