Update Cognito App Client Configuration for dotCMS Staging to Include New Scopes

User Story

As a platform engineer, I want to create (or modify) the required Cognito App Client configuration for the dotCMS staging server to include the following scopes:

• analytics/customer:dotcms
• analytics/cluster:staging1

Acceptance Criteria

• The Cognito App Client configuration is updated to include the specified scopes.
• Authentication and authorization mechanisms function correctly after the update.
• The changes are tested and validated on the staging server.
• Make sure the Falcon team knows about the outputs of this issue:
  • client id
  • client secret
  • customer scope
  • cluster scope

dotCMS Version

main

Proposed Objective

Integrations

Proposed Priority

Priority 2 - Important

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

todefine_

Assumptions & Initiation Needs

• Access to the AWS Cognito configuration for the dotCMS staging server.
• Required permissions to modify the App Client settings.
• No impact on production environments.

Quality Assurance Notes & Workarounds

• Ensure that authentication flows are not disrupted.
• Validate that tokens generated contain the correct scopes.
• Rollback plan in place in case of misconfiguration.

Sub-Tasks & Estimates

• [ ] Review current Cognito App Client settings (1h)
• [ ] Modify Cognito App Client to include new scopes (2h)
• [ ] Validate changes in staging environment (2h)

Start by reviewing the current Cognito App Client settings for the dotCMS staging server, then update the client with the two specified scopes. Validate staging authentication and generated token scopes, and confirm the client ID, client secret, customer scope, and cluster scope are provided to the Falcon team.