Feat license auth separation - #32
Merged
Merged
Conversation
… management features. Updates configuration for SSO claims and CGE credentials. Implements tenant membership roles and updates login screen for organization ID input. Adds new API endpoints for managing members and roles.
…OpenCASE. Adds API endpoints for retrieving, storing, and deleting CGE credentials, including support for tenant-specific API base URLs and token URLs. Updates UI components to integrate CGE credentials functionality and modifies related documentation for clarity on usage and configuration.
…ework functionalities. Introduces new components for searching and managing remote frameworks, including a search panel and item selection panel. Updates the editor canvas to support remote links and improves the handling of external framework data. Additionally, modifies API interactions to accommodate new CGE framework features and optimizes the user interface for better usability.
Contributor
Author
|
This PR includes amendments from PR31 - so I recommend wait until 31 is merged first |
main already contains the earlier CGE work from this branch (squashed as #31), plus #33-#38, so conflicts in the pre-squash CGE files were resolved in favour of main. The branch's own change (c16f5f1, separating public access from license) was re-applied on top and adapted to main's ext:opencase handling: - FileFrameworkStore: publicAccess is read from the verbatim openCaseExtensions via a new getOpenCasePublicAccess() accessor instead of being duplicated onto DocumentMetadata. - ListFrameworks / GetAllCFDocuments: no change needed; main already serves the full ext:opencase object, which now includes publicAccess. - Editor: publicAccess lives on OpenCaseListExtensions and HomeScreen reads it from extensions['ext:opencase'], like sourcePackageURI.
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
2 participants
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.
This PR separates the license and authentication features so they can each controlled independently