* Add ENFORCEABLE_SSO feature flag
* First draft of enforce sso configuration / show single sign on url
* Reading and writing isSSOEnforced + integration with login page
* Enable CI + lint
* Set correct base branch for CI
* Test fix for expected string changed
* Use tenant aware platform url as SSO link
* Bring in latest pro changes
* Lint
* Add useEnforceableSSO mock helper function
* Update configs.spec.ts with coverage for public settings
* Update users.spec.ts with additional tests for isPreventPasswordActions
* Lint
* Update refresh OAuthToken to use correct enum and add case statement
* Prevent SSO users from setting / resetting a password
* Add support for ENABLE_SSO_MAINTENANCE_MODE
* Add typing to self api and build out user update sdk
* Integrate sso checks with user sdk. Integrate user sdk with self api
* Test fixes
* Move self update into SDK
* Lock down maintenance mode to admin user
* Fix typo
* Add health status response and return type signature to accounts.getStatus
* Remove some unnecessary comments
* Make sso save user function non optional
* Remove redundant check on sso auth details provider
* Update syncProfilePicture function name to getProfilePictureUrl
* Update packages/worker/src/sdk/users/events.ts
Co-authored-by: Adria Navarro <adria@revityapp.com>
* Add ENABLE_EMAIL_TEST_MODE flag
* Fix for logging in as sso user when existing user has password already
* Hide password update and force reset from ui for sso users
* Always disable sso maintenance mode in cloud
---------
Co-authored-by: Adria Navarro <adria@revityapp.com>
- Add swc dependencies
- Add transform change to jest.config.ts
- Replace `export =` with `export default` in src code to enable code coverage to work with swc transformer
- Restructure backend-core errors package to allow for exporting error classes with ESM syntax
- Update backend-core to no longer use `export =`, export individual packages instead of replacing with `export default` for backwards compatibility
- Update event publishers to use `export default` - this was required for the `jest.spyOn` usage inside backend-core common mocks
- Restructure some jest.mock usages where declaring the jest.fn as a variable outside of the package mock threw an error
* automation unit tests
* row processor tests
* update executeQuery test
* update groups assertion
* some more worker tests
* plugin tests and tidying up
* linting
* temporarily disable group tests
* more tests
* fix import
* fix backup tests
* add pro mocks to worker
* check for app existence in import test
* test new tsconfig
* testing changes
* Pro test utils (#9020)
* Pro test utils changes
* Add test fixes
* Remove ts-ignore
Co-authored-by: mike12345567 <me@michaeldrury.co.uk>
Co-authored-by: Rory Powell <rory.codes@gmail.com>
