Update /c/{customerId}/{clusterId} Endpoint to Validate customerId in dotCMS Configurator

[victoralfaro-dotcms]

User Story

As a Java developer, I want to change the dotCMS configurator from the https://github.com/dotCMS/internal-infrastructure repo to update the /c/{customerId}/{clusterId} endpoint to consider not only the clusterId field but also the customerId, ensuring that keys are correctly assigned to the right customers.

Acceptance Criteria

• The /c/{customerId}/{clusterId} endpoint logic is updated to check both customerId and clusterId.
• A new method is added to ApiKeyPanacheRepository to look up an entity by clusterId and customerId.
• If no matching entity is found, a new key is created.
• If a matching entity exists, it returns the correct key based on both customerId and clusterId.
• Tests are written to cover all possible scenarios.
• Documentation is updated accordingly.

dotCMS Version

main

Proposed Objective

Core Features

Proposed Priority

Priority 2 - Important

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

to_define

Assumptions & Initiation Needs

• The current implementation only considers clusterId, leading to key mismatches.
• The ApiKeyPanacheRepository supports adding a new lookup method.
• No major architectural changes are needed to implement this fix.

Quality Assurance Notes & Workarounds

• Ensure unit and integration tests validate the new logic.
• Verify that no performance degradation occurs due to the additional lookup parameter.

Sub-Tasks & Estimates

• Implement new lookup method in ApiKeyPanacheRepository (6h)
• Update /c/{customerId}/{clusterId} endpoint logic (6h)
• Final review and approval (2h)