The Boeing Company

David Richard Bowman

Preston R Barbare

Mark James Boyer

Dale R Agajanian

Mary Kay Van De Vanter

Frank R Ellis, Iv

Alexander J Smock

James P Caruso

Melissa Ohlandt

A device includes one or more processors configured to receive, from a user device, an authentication request including credentials of a user. The one or more processors are also configured to obtain user attributes of the user from one or more user data records associated with one or more identity systems. The one or more processors are further configured to obtain one or more roles of the user based on one or more membership lists. The one or more processors are also configured to generate an authentication token indicating the user attributes and the one or more roles.

System architecture for secure highly available microservice applications with decentralized authorization using hybrid attribute authority tokens used for security enforcement in cloud platforms

A device includes one or more processors configured to receive, from a first service, a first access request to request access to a second service on behalf of a user, wherein the first access request includes a user identifier of the user and a first service identifier of the first service. The one or more processors are also configured to, based on determining that the user has granted authorization to the first service to access the second service on behalf of the user, generate a proxy authentication token based on the first access request. The one or more processors are configured to send a second access request to the second service, wherein the second access request includes the first service identifier and the proxy authentication token.

System architecture for secure highly available microservice applications with decentralized authorization and delegated authorization controls in cloud platforms

A server computing device including one or more server memory devices storing a relational database. The server computing device further includes one or more server processing devices configured to receive an ephemeral graph database request. The ephemeral graph database request indicates a selection of data stored in the relational database. The processing devices generate an ephemeral graph database that encodes the selected data in a graph structure and store the ephemeral graph database in binary large object (BLOB) storage at the one or more memory devices. The processing devices receive instructions to apply a graph analytics algorithm at the ephemeral graph database. The processing devices read the ephemeral graph database from the BLOB storage and apply the graph analytics algorithm to the ephemeral graph database to generate a graph analytics result. The processing devices output the graph analytics result and delete the ephemeral graph database from the BLOB storage.

Ephemeral graph database

Systems, devices, and methods for smart chain charging of electric vehicles. A system has a dock and one or more electric vehicles supporting rechargeable batteries. One or more electric vehicles may be coupled in series in a smart chain at the dock. Each electric vehicle has a charger with a plug and a receptacle. The plug may couple to a dock receptacle, if the vehicle is first in the smart chain, or to a receptacle on a neighboring electric vehicle at the end of a smart chain of vehicles electrically coupled to the dock. The receptacle may receive a plug of a neighboring electrical vehicle. Each charger may include an interface, battery charger and a battery monitor. The interface may carry power and transfer data into and out of the charger along the smart chain. Each battery monitor may output battery monitor data and receive battery charging control information.

Systems and methods for smart chain charging of rechargeable batteries in electric vehicles

Described are new methods and systems for provisioning factory devices in enterprise network systems using specially configured Factory Device Provisioning (FDP) portals, FDP modules, which is used for supporting various operations of the FDP portals, and enterprise device management (EDM) modules. In some examples, an EDM module stores a device-information set (e.g., an asset tag), while an FDP module stores a device-location list and a device profile, corresponding to a certain factory device. An FDP portal allows a user, through a user interface provided by the DRP portal, to retrieve and review this information without directly interacting with the EDM module. The FDP portal then allows the user to initiate a device enrollment request for the factory device. The FDP module generates a device-configuring information, which is presented by the FDP portal and used for connecting the factory device to the enterprise network system.

Growing community of inventors

Charleston, SC, United States of America

David Richard Bowman