US 2026/0301036 A1Published application

System, apparatus and method for event publishing and access management

AssigneeW.W. Grainger, Inc.

InventorsPradeep NAGISETTY, Michael GORE, Kannan PARAMASIVAM, José GONZALEZ, Rocío Elizabeth MERA SUÁREZ

Life of this patent

Estimating the term…

Loading patent…

Abstract

A system, apparatus and computer-enabled method of managing an event data product catalog, comprising authenticating users through a developer platform interface or standalone service using [bearer tokens and group membership claims from an enterprise identity provider to determine access permissions; validating event topics against quality standards and required business metadata, including creation date, owning team, roster ID, and contact information; enriching validated topics with metadata about serialization format and data sensitivity through a data enrichment API; publishing validated and enriched topics as event data products by tagging them in the broker system, making them discoverable based on environment, domain, and ownership filters; managing access control through automated infrastructure-as-code generation, wherein access requests trigger creation of code snippets submitted as pull requests to event owners' provisioning repositories; and maintaining catalog consistency through automated workflows that integrate authentication, validation, and version control to ensure discoverable events remain production-ready and properly authorized.

Claims20

Dependent claims

A computer-enabled method of managing a content catalog in event-based computer architecture, comprising:

Listening, with a computer, to a content event published to an event stream;
Detecting, via the computer, the content event for catalog items, the content event being published by an information management system and stored in a log for subsequent use by a second event consumer, and the content event being associated with a set of retail data, wherein the content event is received from the information management system and from an event producer;
Sending, by the computer, a request to enrich a set of content data, the set of content data originally including raw data, the enriching occurring in real time after detection of the set of content data and being performed by a data enrichment application programming interface (API);
Receiving, by the computer, a set of enriched content data and publishing an enriched data event by the event producer for use by the second event consumer, the set of enriched content data including the enriched draft content data and the enriched scheduled content data, the enriched content data being converted from a raw format into an enriched format , wherein the information management system includes a datastore configured to temporarily store the content data and a long term storage configured to persistently store the content data, and wherein the set of enriched available content data is stored in the long term storage and wherein the enriched draft content data is stored in the datastore;
aggregating, by a data aggregator, the enriched draft content data and the scheduled content data from the information management system and making the enriched draft content available and the processed content data for consistent catalog presentation;
analyzing, via the computer, the set of enriched content data;
and
maintaining, via the computer, catalog consistency across a set of sales channels using at least a catalog management algorithm that provides for improved product discovery based on the enriching and aggregating the set of content data.

5 more elements

An apparatus for managing an event data product catalog in an event-driven computer architecture, comprising:

a Backstage platform plugin configured to provide a user interface with at least a separate view for a team-owned events and a published event product;
an authentication module configured to:
validate at least an JSON web tokens containing an Active Directory group membership through an Okta interface with a Team Details service to map at least a security group to access permissions, and determine a topic visibility and a publishing right based on a validated group membership;
a hexagonally architected backend comprising:
an application layer configured to process requests from a user interface module, a domain layer configured to validate a strongly typed objects and maintain business logic isolation, and an infrastructure layer configured to interface with at least a Kafka clusters and source control systems;
a topic validation module configured to:
verify required business metadata including a creation date, an owning team, a roster ID, and a contact information, check a topic version control status and at least a deprecation tags, and ensure the topics meet quality standards before publication as an event data product;
an access control manager configured to:
process access requests specifying a service accounts and a required permission, invoke a Code Snippet Service to generate infrastructure-as-code, create a repository branch through a Pull Request Service, and submit generated code as pull requests to an event owners' provisioning repositories;
a discovery interface configured to:
provide filtered views of event products by environment, domain, and ownership, implement pagination for scalable result presentation, exclude deprecated versions from a published catalog, and maintain separate displays for team events and available event products;
and
a metadata enrichment module configured to:
tag topics with serialization format and data sensitivity indicators, maintain version control information, track cross-access implementations, and ensure consistent presentation of enriched event data products across the catalog.

11 more elements

A system for managing an event data product catalog in an event-driven computer architecture, comprising:

a catalog management server comprising at least one processor and memory storing instructions that, when executed, further configure the processor to:
implement a developer platform interface providing separate views for team-owned events and published event products;
execute an authentication service that validates bearer tokens containing group membership claims from an enterprise identity provider, interfaces with a Team Details service to map security groups to access permissions, and determines topic visibility and publishing rights based on validated group memberships;
operate a hexagonally architected service comprising an application tier processing requests from the developer platform interface, a domain tier validating strongly typed objects and maintaining business logic isolation, and an infrastructure tier interfacing with Kafka clusters and source control systems;
perform topic validation by verifying required business metadata including creation date, owning team, roster ID, and contact information, checking topic version control status and deprecation tags, and ensuring topics meet quality standards before publication as event data products;
manage access control by processing access requests specifying service accounts and required permissions, invoking a Code Snippet Service to generate infrastructure-as-code, creating repository branches through a Pull Request Service, and submitting generated code as pull requests to event owners' provisioning repositories;
provide a discovery service that generates filtered views of event products by environment, domain, and ownership, implements pagination for scalable result presentation, excludes deprecated versions from a published catalog, and maintains separate displays for team events and available event products;
and execute a metadata enrichment service that tags topics with serialization format and data sensitivity indicators, maintains version control information, tracks cross-access implementations, and ensures consistent presentation of enriched event data products across the catalog.

5 more elements

Dependencies are inferred from the claim text.