Skip to content

Feature/cmg 686#930

Closed
shobhitupadhyayy wants to merge 11 commits intodevfrom
feature/cmg-686
Closed

Feature/cmg 686#930
shobhitupadhyayy wants to merge 11 commits intodevfrom
feature/cmg-686

Conversation

@shobhitupadhyayy
Copy link
Contributor

No description provided.

- Introduced a new build.sh script for region selection and OAuth login.
- Added app.json to .gitignore and included manifest.json in API .gitignore.
- Updated package dependencies for improved functionality.
- Implemented saveOAuthToken endpoint for secure token handling.
- Enhanced region configuration and API host management in constants.
- Added error handling and logging improvements in auth service.
…cies

- Removed redundant variables for client_id and client_secret in saveOAuthToken function.
- Updated logging to use a centralized logger instead of console methods.
- Removed unnecessary deletion of code_verifier from the request session.
- Updated package.json to remove outdated "api" dependency.
- Modified build.sh to append '/v2/auth/save-token' to the redirect_uri.
- Updated auth.service.ts to use the correct redirect_uri for token requests.
- Ensured consistency in region configuration and API endpoint handling.
- Added new endpoints for retrieving app configuration and checking SSO authentication status.
- Updated authentication service to handle SSO tokens and access tokens more effectively.
- Enhanced error handling for SSO-related operations.
- Updated UI components to support SSO login and added corresponding styles.
- Refactored API service calls to accommodate new SSO logic and improved token management.
- Added logout endpoint to the authentication service for user session management.
- Updated UI components to handle logout actions and provide user feedback during the process.
- Enhanced error handling for SSO-related operations and improved user experience during authentication.
- Introduced app.json for configuration management and updated related services to utilize this configuration.
- Refactored authentication logic to streamline SSO checks and improve overall flow.
- Added app.json to the main .gitignore to prevent tracking of configuration files.
- Included manifest.json in the api/.gitignore to exclude it from version control.
- Added isSSO property to the Project interface for better SSO handling.
- Introduced requestWithSsoTokenRefresh utility to streamline SSO token management across services.
- Updated various service methods to utilize SSO token refresh logic, improving authentication flow.
- Refactored API calls in org.service.ts, migration.service.ts, and user.service.ts to support SSO.
- Enhanced pagination utility to accommodate SSO token handling for paginated requests.
- Updated configuration handling to prefer updated_at for OAuth token management.
- Changed default value of cmsType to 'cmsType' for clarity.
- Updated localPath default to 'localPath' to standardize configuration settings.
@shobhitupadhyayy shobhitupadhyayy requested a review from a team as a code owner January 28, 2026 07:21
@gitguardian
Copy link

gitguardian bot commented Jan 28, 2026

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
25710850 Triggered Generic High Entropy Secret 8fb61c2 api/manifest.json View secret
25710851 Triggered Generic High Entropy Secret 8fb61c2 app.json View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant