Atlassian Corporation Pty Ltd.

Atlassian Inc.

Atlassian Us, Inc.

Jeffrey Lawrence Farber

Sidney Gee-Lake Shek

Diogo Correa Lucas

Deepak Kulkarni

Jonathan Paul Gilbert

Rahul Revo

Pramod Shashidhara

Max Robert Morton

A computer-implemented method includes receiving permission data from an application server. The permission data is for an account to access a software application of a plurality of software applications, and the application server is configured to provide the software application. Responsive to receiving the permission data from the application server, storing the permission data in a native database. Receiving a request to grant the account access to the software application. Determining whether the database stores the permission data for the account to access the software application. In response to determining that the database stores the permission data, granting access to the account to access the software application.

Managing content authorization in a federated application system

Methods, apparatuses, or computer program products are disclosed providing for the dynamic generation and traversal of object dependency data structures. Examples enable generation of service dependency work graph structures for service dependencies associated with one or more services and dynamic replacement of service instances based upon traversal of the service dependency work graph data structures.

Apparatuses, methods, and computer program products for dynamic generation and traversal of object dependency data structures

Various embodiments are directed to a federated network and database platform that is configured to sequence client write events occurring among several autonomous software applications. The federated network and database platform includes a client event sequencing server that is configured to receive a migration corpus of client write events from at least one software application server and assign a back-date time stamp to each client write event of the migration corpus. Upon receiving a new client write event associated with the software application, the client event sequencing server is configured to assign a current time stamp to the new client write event and store the new client write event to a client event sequencing database in a manner that positions the new client write event relative to the back-dated migration corpus of client write events.

Client write event sequencing system in a federated database platform

Methods, apparatuses, or computer program products provide for generating one or more service object criticality scores for service objects based on service dependency work graph structures. A service dependency work graph structure may be retrieved from a service object repository. The service dependency work graph structure may be traversed. Based at least in part on a strength measure associated with each service object relationship of one or more service object relationships associated with each unique service object identifier, one or more service object criticality scores for the unique service object identifier may be generated in relation to each other service object identifier of the plurality of service object identifiers.

Methods, apparatuses, or computer program products provide for identifying service dependency data residency type conflicts associated with service object identifiers based on service dependency work graph structures and service guarantees. A service dependency work graph structure may be traversed. Based at least in part on one or more service dependency data residency types associated with each service object relationship of one or more service object relationships associated with a service object identifier, those service object identifiers may be identified that are associated with service dependency data residency types in conflict with a data residency requirement associated with the resource detection.

Systems, apparatus, and methods for tracking and sequencing client events in a federated computer network are discussed herein. Various embodiments provide a computer-implemented method for assigning timestamps to client events received by nodes within the network and appending node identifiers to the timestamps to create node time signatures for the client events to facilitate updating of a client event database. Still other embodiments provide methods for comparing a last event node time signature to a recently received node time signature and generating an updated node time signature in view of the same. Such embodiments address client event sequencing problems that tend to plague federated and distributed networks as they expand in scale, geographic distribution, complexity, and involve programmatic client event generating services such as credential management services.

Node-indexed system, apparatus and method configured to sequence client events within a peer-to-peer network

A computer-implemented method includes receiving a first request to grant an account access to a software application of a plurality of software applications, and determining whether a native database stores first permission data for the account to access the software application. This example method further includes, in response to determining that the database does not store the first permission data: sending, via a network to an application server configured to provide the software application, a second request for second permission data for the account to access the software application; responsive to sending the second request to the application server, receiving the second permission data from the application server; responsive to receiving the second permission data from the application server, storing the second permission data in the database; and granting, in accordance with the second permission data, access to the account to access the software application.

Growing community of inventors

San Mateo, CA, United States of America

Jeffrey Lawrence Farber