Tenant Configuration via API for Dynamic Cloud Application Customization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Cloud-computing service providers face challenges in customizing features for multiple entities using the same application without exposing sensitive systems or intellectual property, as modifying applications is resource-intensive and requires skilled personnel.
Innovation Solution
A system that allows tenants to customize application configurations through a Tenant Application Program Interface (API) during provisioning, where a payload defines available features, and logic determines the configuration to apply at runtime based on a resource identifier, enabling customized feature sets without direct access to sensitive systems or source code.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the cloud-computing service provider modifies the application according to each user's desired features, then the user gets customized features, but the resource and time consumption increases significantly
Solution Approach 1:
The application is segmented into multiple configurable modules or features that can be independently enabled or disabled. Each feature is defined as a separate configuration option that can be toggled on or off based on user requirements, allowing customization without modifying the core application code.
Solution Approach 2:
The application is pre-configured with a comprehensive set of optional features during deployment. Users can select and enable only the features they need through configuration files or administrative interfaces, rather than requiring post-deployment modifications. This preliminary setup eliminates the need for resource-intensive customization processes.
2Adaptability or versatility
If the user is given access to sensitive systems and source code for customization, then the user can adapt the application, but the cloud-computing resource service provider is exposed to intellectual property theft
Solution Approach 1:
The customization capability is extracted from the core application source code and implemented as external configuration files or parameters. Users interact with configuration interfaces that modify behavior through settings rather than code changes, keeping the sensitive source code isolated and protected on the service provider's systems.
Solution Approach 2:
An intermediary configuration layer is introduced between the user and the application source code. This layer allows users to customize features through configuration files or administrative interfaces without direct access to the underlying source code, acting as a protective barrier that prevents intellectual property exposure while enabling adaptation.
3Adaptability or versatility
If the user procures or redirects skilled computer scientists to understand and adapt the application, then the customization can be achieved, but the cost and complexity increase
Solution Approach 1:
The application includes built-in configuration interfaces and documentation that enable users to perform customization themselves without requiring external expert assistance. The configuration process is designed to be user-friendly, with clear options and explanations, allowing non-expert users to adapt the application to their needs through self-service.
Data Source
AI summary
Embodiments allow a tenant to customize a configuration that is used in accessing an application over the cloud. At a provisioning time, a user accesses a tenant Application Program Interface (API) and creates a customized configuration including a payload that defines particular features to be available from the application. Such features can include but are not limited to available buttons, toolbar options, and pages. During a runtime subsequent to the provisioning, an input to the application (such as a URL) is received from the tenant. Logic is executed to determine whether to apply the custom configuration or another configuration (e.g., default or other predefined) from a list. Based upon the configuration, the application renders output to the user according to the particular features. Particular embodiments may recognize a Line of Business (LoB) parameter of a URL input to the application in order to provide a configurations customized by the tenant.