Access Credential Event Logging for Historical State Recovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing access credential management systems struggle to efficiently track and manage historical state transitions and modifications, leading to challenges in accommodating post-hoc feature additions and data loss, particularly in non-eventing data stores.
Innovation Solution
Implementing an event logging engine that subscribes to event notifications for access credential requests, creating and appending event objects to immutable event logs, allowing for the capture and replay of historical state transitions, enabling efficient management of access credential requirements and features on a post-hoc basis.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If traditional non-eventing data stores are used for access credential management, then system simplicity is maintained, but historical state transitions cannot be tracked and data loss occurs
Solution Approach 1:
The system performs preliminary action by capturing and storing every state transition event in an immutable event log before the traditional data store can lose the information. Event sourcing records all changes to access credentials in chronological order, ensuring historical data is preserved permanently rather than relying on the traditional data store to maintain it.
Solution Approach 2:
The patent introduces an event log as an intermediary layer between the access credential management system and the traditional data store. This event log acts as a mediator that captures all state transitions and provides a complete historical record, allowing the system to recover any past state without modifying the original data storage approach.
2Reliability
If event logging engine is implemented to track all access credential events, then comprehensive data capture is achieved, but system complexity increases
Solution Approach 1:
The system segments the data management functionality into distinct components: an event logging engine that captures state transitions, an immutable event log that stores events, and a traditional data store that maintains current state. This segmentation allows each component to specialize in its function, improving reliability while making the overall complexity manageable through clear separation of concerns.
Solution Approach 2:
The event log serves multiple functions simultaneously: it acts as a complete historical record, a recovery mechanism for lost data, a audit trail for security purposes, and a source for reconstructing any past system state. This multi-functionality justifies the added complexity by providing comprehensive data capture and multiple benefits from a single component.
3Stability of the object's composition
If immutable event logs are used to store historical records, then data integrity is maintained, but storage requirements increase
Solution Approach 1:
The system creates copies of state transition events in the immutable event log without replacing the original data in the traditional data store. Each event is recorded as a discrete copy of the change that occurred, allowing the system to maintain data integrity through multiple copies while managing storage by only storing the essential event information rather than redundant data.
4Adaptability or versatility
If post-hoc feature additions are enabled through event sourcing, then system adaptability improves, but implementation complexity increases
Solution Approach 1:
The system implements dynamics by allowing the interpretation and processing of event log data to change over time without modifying the underlying event storage structure. New features can be added by implementing different ways of querying and processing the immutable event log, enabling the system to adapt to new requirements while maintaining the stability of the core event sourcing mechanism.
Data Source
Figure 1A~1B
Figure 2
Figure 3
AI summary
Described embodiments relate to a computer-implemented method comprising: receiving, from an authorization server, an access credentials read request associated with a user. The access credentials read request comprises one or more access credential identifiers and one or more parameter values, wherein the one or more parameter values are derived from a current state of a set of requirements for authorizing modifications to access credentials. The method further comprises traversing a first event log associated with the user to determine one or more access credential values associated with the respective one or more access credential identifiers based on the one or more parameter values and transmitting, to the authorization server, the one or more access credential values.