Custom Restriction Rule Placeholders in Access Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current business and enterprise systems lack the ability for customers to define custom restriction rules, forcing them to rely on predefined access control rules that may not align with their specific business needs, leading to inefficient access management and the need for frequent software updates to accommodate unique organizational requirements.
Innovation Solution
The system provides customers with the ability to create custom restriction rules through placeholders, allowing them to associate custom code with business roles, enabling the derivation of access objects and authorizations based on customer-specific master data, thereby tailoring access controls to their unique needs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If predefined access control rules are used, then system simplicity and ease of operation are maintained, but adaptability to custom business requirements deteriorates
Solution Approach 1:
The access control system is segmented into predefined rules (for common scenarios) and custom rule placeholders (for business-specific scenarios). This allows users to select from standard options when appropriate while providing a mechanism to customize rules when business needs differ, thus maintaining ease of operation while improving adaptability.
Solution Approach 2:
Custom rule placeholders act as intermediaries between the predefined access control framework and custom business requirements. These placeholders provide a standardized interface for customers to define custom rules without disrupting the overall system architecture, enabling adaptability while preserving system simplicity.
2Adaptability or versatility
If custom restriction rules are enabled, then adaptability to business needs is improved, but device complexity increases
Solution Approach 1:
The complexity of custom rule definition is segmented and encapsulated within placeholder structures. Customers interact with simplified placeholders rather than raw complexity, and the system handles the complex evaluation logic separately from the user interface, thus managing complexity while maintaining adaptability.
Solution Approach 2:
The custom rule placeholder serves as an intermediary layer that abstracts the complexity of access control evaluation from the user. Customers define rules through simple placeholder associations without needing to understand the underlying complexity of master data relationships and evaluation logic.
3Reliability
If predefined rules are used, then system stability is maintained, but loss of time for software updates increases
Solution Approach 1:
The system transitions from static predefined rules to dynamic rule configuration where customers can adapt rules to changing business needs without system updates. The framework supports runtime configuration of custom rules, eliminating the need for time-consuming software updates when business requirements change.
Solution Approach 2:
Custom rule placeholders are prepared in advance within the system framework, allowing customers to quickly configure and activate custom access control rules without requiring system updates. This preliminary preparation of configuration capabilities reduces time loss when adapting to new business needs.
Data Source
AI summary
Extensibility tools are provided to customers for defining custom restriction rules for enhanced access controls. In an example method, a listing of restriction rules available for a business role are presented. The restriction rules include predefined restriction rules and at least one custom restriction rule placeholder, wherein the predefined restriction rules are delivered with the enterprise software system the at least one customer restriction rule placeholders are associated with a link to custom code developed as a customer-specific restriction rule. A selection of a particular custom restriction rule is received and associated with the particular business role. When evaluating the restriction rule, the custom code and a set of master data defined in the custom code is accessed to determine restrictions for each of the end users associated with the business role. A set of access objects are derived for each user based on the information.