Open
Conversation
…d update user schema
…d update user schema
…outer and clean up organization router by removing enterprise settings methods
…y validation in the API to require at least one of enableEnterpriseFeatures or licenseKey.
…omponent, enhance license key validation and activation in the API, and implement new methods for activating and deactivating license keys.
…g to provide more informative messages for validation, activation, and deactivation processes.
… current user's license key and improve error handling for user validation and missing license keys.
… server-side validation and layout integration, and update the sidebar menu to include a link for accessing the License settings.
…idation, implement query to check for valid license keys, and improve UI feedback during license key checks.
…license key management, update contact link to the official site, and enhance user feedback with improved loading states for activation and validation processes.
…ate OIDC provider registration dialog, and update dependencies for better-auth to version 1.4.18. Enhance user interface with new SSO menu item and improve database schema for SSO providers.
…ew SAML provider registration dialog with form validation using Zod, integrate it into the SSO settings page, and refactor the OIDC registration dialog to utilize React Hook Form for improved state management and validation.
…e and EnterpriseFeatureLocked components to manage access to enterprise features based on license validation. Integrate the EnterpriseFeatureGate into the SSO settings page to conditionally render SSOSettings based on license status.
…e key validation logic to ensure proper handling of enterprise licenses, including new cron job for refreshing license validity. Introduce new SQL migration for isValidEnterpriseLicense column and refactor related API procedures for better error handling and user feedback.
… backup cron job initialization: Deleted the cron endpoint for refreshing license validity and added the initialization of enterprise backup cron jobs in the server setup. Updated the enterprise cron job logic to filter users based on license key and enterprise feature status.
…on job setup by consolidating user retrieval and validation logic into a single scheduled job. Updated the schedule to run every 3 days and removed redundant checks for user length.
…rOidcDialog and RegisterSamlDialog components, replacing it with a call to invalidate the list of SSO providers after successful registration. Update SSOSettings to reflect these changes, enhancing the overall state management and consistency across the dialogs.
…Settings, including OIDC and SAML configuration parsing. Implement loading states for SSO sign-in on the homepage and expose a public API for listing SSO providers. Update UI components for better user experience and maintainability.
… for existing admin presence before creating a new admin, ensuring proper error handling for duplicate admin creation. Update cloud condition to account for admin presence.
…finitions in auth-schema2.ts for future refactoring and cleanup.
…Hub, Google, and SSO, enhancing user authentication methods. Update SSO settings to conditionally render based on enterprise features and improve the overall login experience on the homepage.
…sterSamlDialog components to use field arrays for managing multiple domains and scopes. Enhance validation logic to ensure at least one domain is provided. Improve UI for adding and removing domains and scopes dynamically, streamlining the user experience in SSO configuration.
…etch SSO provider details from the database. Update authentication logic to include SSO domains in the server settings, enhancing SSO functionality and user experience.
…-in components into the registration page, allowing cloud users to register using these methods. Update UI to present alternative registration options, enhancing user experience.
…ponents - Refactored SSO registration logic in `register-oidc-dialog` and `register-saml-dialog` to use a new mutation method. - Removed unused imports and error handling for registration failures. - Added foreign key constraint for `organization_id` in the `sso_provider` table. - Introduced new SSO schema and updated user relations to include SSO providers. - Enhanced authentication flow to support SSO provider registration.
…rity - Updated the `listProviders` query to filter SSO providers by both organization ID and user ID. - Modified the provider validation logic to ensure that only relevant providers are returned for the authenticated user.
…on management - Added new disabled paths for organization creation, update, and deletion to enhance security in the authentication flow.
- Refactored `register-oidc-dialog` and `register-saml-dialog` to accept an array of domains instead of a single domain string. - Enhanced server-side validation to check for duplicate domains across registered providers. - Updated SSO schema to reflect the change from a single domain to an array of domains, including validation for domain format.
…st handling - Included a new Okta domain in the array of allowed domains for SSO authentication. - Modified the SSO request handling logic to return early if the request is an SSO callback, enhancing the flow of authentication.
…rity - Updated the method name from `forgetPassword` to `requestPasswordReset` in the password reset flow to better reflect its functionality.
- Added authorization checks to ensure only users with the "owner" role can activate or deactivate license keys. - Updated the menu item visibility logic to simplify role checks for admin and owner users. - Commented out the cloud environment redirection logic in the license settings page for future consideration.
…iders - Updated the mapping logic in `register-oidc-dialog` to differentiate between Azure and other identity providers. - Simplified the mapping structure for user attributes based on the issuer, improving flexibility in handling various OIDC providers.
…metadata handling - Added support for IdP metadata XML in the SAML registration dialog, allowing users to paste full metadata for configuration. - Updated the callback URL and audience handling to dynamically incorporate the base URL. - Refactored the SSO settings to enable SAML provider registration and improved the display of callback URLs based on provider details. - Enhanced trusted origins configuration in the authentication logic to include additional domains for development and production environments.
- Commented out the old database URL for security reasons. - Updated the database connection string to use the Docker service name for PostgreSQL, ensuring proper connectivity in containerized environments.
…cense settings page for future consideration
…readability - Changed the export of the `handler` and `api` constants to local scope for better clarity. - Enhanced the trusted origins logic by restructuring the code for improved readability and maintainability. - Commented out the cloud environment redirection logic for future consideration, aligning with previous changes in the codebase.
…validation - Updated user context to include `enableEnterpriseFeatures` and `isValidEnterpriseLicense` properties. - Modified request validation to set these properties based on user data, enhancing enterprise feature management. - Adjusted the enterprise procedure to check user flags directly from the context instead of querying the database.
- Added a new service to fetch SSO providers from the database, including relevant fields such as id, providerId, issuer, domain, oidcConfig, and samlConfig. - This functionality will support future enhancements in SSO integration.
- Deleted the import statement for `getSSOProviders` and the associated logic for fetching issuer origins from SSO providers. - This cleanup improves code clarity by removing unnecessary dependencies and streamlining the trusted origins configuration.
…ment environments - Modified the database URL assignment logic to differentiate between production and development environments. - Ensured that the correct database URL is used based on the NODE_ENV variable, improving deployment flexibility.
- Introduced a new mock database setup file to simulate database interactions during tests. - Updated Vitest configuration to include the mock setup file, enhancing test reliability and isolation.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is this PR about?
Introduce License Key Validation for enterprise and SSO
Checklist
Before submitting this PR, please make sure that:
canarybranch.Issues related (if applicable)
Screenshots (if applicable)