Abstract: Multiple systems, methods, and computer program product embodiments for password-less authentication using key agreement and multi-party computation (MPC). In one or more embodiments, following an authentication request received by a host computing device, the host computing device and a user computing device generate a shared key using a key agreement algorithm. Then, the host computing device generates a challenge that is encrypted using the shared key and transmitted to the user computing device. The user computing device decrypts the challenge after regenerating the shared key and sends the decrypted result to the host computing device as the challenge response. The authentication request is granted by the host computing device if the challenge and the challenge response match. New keys and a new challenge are generated for each authentication request. This process relies on public key cryptography eliminating the needs for passwords.

Abstract: Disclosed herein are system, method, and computer program product embodiments for providing asynchronous backend processing of complex, time consuming, and/or expensive jobs. A command line interface (CLI) provides a command interface between a user and a backend processing server. The CLI sends a job request to the backend server, which immediately replies to the request with a confirmation message that includes a job identifier. This response is sufficient to allow the CLI to end its wait for the job response. Meanwhile, the backend server carries out the job by parsing the job into component tasks according to a declaration file and assigns those different tasks to different work servers. The backend server functions as a master server, tracking the statuses of the different tasks and assigning out new tasks until the job is complete. An overall job status is provided to the CLI upon request by referencing the job identifier.

Abstract: Disclosed herein are system, method, and computer program product embodiments for self-paced migration of an application programming language (API) gateway. An embodiment operates by receiving a functional test suite corresponding to an application programming interface (API). The embodiment generates a knowledge graph of information by combining a test result graph of information based on a result of execution of one or more tests in the functional test suite with a metadata linked graph of information based on metadata corresponding to the one or more APIs. The embodiment then generates an alert message corresponding to the function test suite based on the knowledge graph of information.

Abstract: Disclosed herein are system, method, and device embodiments for a data bridge adapter in a data integration platform that models any application programming interface as an entity-relationship model. This technique allows an individual using an integration platform to map and transform the entity-relationship model without having to create any custom code. The user may specify target parameters as part of an ETL process, and the entity relationship model may allow appropriate data and API calls to be generated to pass the data to the specified target. By creating an entity-relationship model from any API, the technique further supports versioning, schema change resolution, compatibility detection and other features. Furthermore, data visualization software may use the entity-relationship model to allow users to explore and analyze the data represented in the entity-relationship model.

Abstract: Disclosed herein are system, method, and computer program product embodiments for automatically discovering an API for publishing within a data repository. A discovery tool is used either on a server computer or a customer computer to examine the files stored in the data repository. A search of the repository is conducted to identify root API files that form the basis of an API. A first examination is conducted in which the files are examined for common indicia associated with known API standards. Then a second examination is done of the root API candidates found in the first examination to identify which of the root API candidates is actually a root API. Once the root API has been located, it is executed in a computer environment, and its dependents are detected. Once all the necessary API files have been located, they are packaged and automatically published.

Abstract: Disclosed herein are system, method, and computer program product embodiments for providing a universal coding language and construct for an application programming language (API) environment. In the environment, a standard language with a predefined and universal format is used for each of the different internal code modules. A translator is then provided in order to translate the standard language to the proprietary language of specific gateways or other vendor products. In some embodiments, a parser is used to in order to convert the code modules to an internal model. The internal model allows a user to visualize or otherwise understand the configuration that has been coded, and to make any necessary modifications.

Abstract: A computer-based system may be configured to collect metadata and/or the like indicative of all the metrics exposed from a data pipeline (e.g., an ETL pipeline, etc.) and transform the metrics into a single group of metrics user-facing, user-specific, user-configured, and/or the like metrics that allow the maturity and quality of data and/or data records to be analyzed and/or displayed. Collected metrics can be agnostic of a source data flow component of a data pipeline and/or resource technology (e.g., API, etc.). Collected metrics may indicate a measure of data freshness, data duplication, new data records, updated date data records, data errors, and/or the like.

Abstract: Disclosed herein are system, method, and computer program product embodiments for implementing automatic taxonomy tags in an API microgateway. The API microgateway may receive a plurality of API requests for an API managed by a customer in a period of time and route the plurality of API request to an instance of the API according to a policy of the API. The API microgateway may aggregate metrics information related to the plurality of API requests. The aggregated metrics information may include request features, response features, policy features, and performance features. In response to a cluster of the metrics information corresponding to a tag in a tag prediction system, the aggregated metrics information may be labeled with the tag. The tag and the aggregated metrics information may be added to an access log and sent to the customer.

Abstract: According to some implementations, while a proxy routes production traffic to a first application (app) version that runs in a plurality of container orchestration system (cos) pods having first app version containers, configuration information is received including an identification of a second app version container image for a second app version. The second app version is an updated version of the first app version. Cos pods having second app version containers are brought up based on the second app version container image identified in the configuration information. Test and/or warmup traffic is caused to be routed to the second app version containers. Responsive to an indication regarding the routing of the test and/or warmup traffic to the second app version, causing a transition to sending production traffic to the second app version containers instead of to the first app version.

Abstract: Disclosed herein are system, method, and computer program product embodiments for automatically cataloging updated Application Programming Interface (API) specifications. The API specifications may have been previously published to an application exchange platform. An automatic cataloging tool installed at an API development system may identify an updated API specification committed to an API specification repository. To validate that a change has been made, the automatic cataloging tool may compare the updated specification, metadata, and/or referenced documentation files to an API specification previously posted to the application exchange platform. In response to determining that the API specifications differ, the automatic cataloging tool may transmit the updated API specification to the application exchange platform. The application exchange platform may then replace the previous API specification with the updated API specification for client devices to view.

Abstract: A mobile application development environment may be maintained in association with a computing platform. A request to produce a first mobile application with a first security policy may be processed. The first mobile application may be automatically produced. The first security policy may be integrated with the first mobile application during creation of the first mobile application. The first mobile application may be provided to a mobile application provider. The first security policy may be included in the first mobile application when the first mobile application is downloaded from the mobile application provider.

Abstract: There is provided computer implemented method for detecting and reducing or removing bias for generating a machine learning model, comprising: prior to generating the machine learning model: receiving a training dataset, comprising target inputs, each comprising parameters and labelled with a corresponding target output, wherein at least one of the parameters of at least of the target inputs comprises a sensitive parameter indicative of the corresponding target input assigned to a sensitive group that is potentially biased against other target inputs that are excluded from the sensitive group, analyzing the training dataset to identify target inputs affected by label bias when a statistically significant difference is detected between target inputs assigned to the sensitive group and target inputs excluded from the sensitive group, correcting labels of the target inputs affected by label bias, and generating the machine learning model using the corrected labels.

Abstract: A method and system of data deduplication for data streams in a multi-tenant system. The method receives, at a data accuracy manager, an event from an activity tracking component, determine whether the event is recorded in a probabilistic model that tracks previously received events from the activity tracking component, where the probabilistic model can accurately identify the event has not been previously received with a possible false positive response where the event has been previously received, determines whether information for the event is stored in a metric storage, where the metric storage is a database of metrics derived from the previously received events, and discards the event in response to determining that the event is recorded in the probabilistic model and in the metric storage.

Abstract: There are provided mechanisms and methods for maintaining data stored in a data structure. These mechanisms and methods for maintaining data stored in a data structure can provide maintenance operations with improved efficiency, functionality, etc.

Abstract: Provided herein are system, methods and computer program products for using a bot server for initiating and controlling bot instances, specifically conversation bot instances at client devices for interacting with users associated with the client devices. The bot server may communicate with a remote cloud service providing bot services for initiating and operating the bot instances to retrieve logic metadata used to control the bot instances and may use this metadata to initiate and control one or more bot instances at the client devices to interact with the associated users. In particular, the bot server may be deployed at a network edge in close network proximity to the client devices.

Abstract: In accordance with embodiments, there are provided mechanisms and methods for appending data to large data volumes in a multi-tenant store. These mechanisms and methods for appending data to large data volumes can enable embodiments to provide more reliable and faster maintenance of changing data. In an embodiment and by way of example, a method for appending data to large data volumes is provided. The method embodiment includes receiving new data for a database. The new data is written to a temporary log. The size of the log is compared to a threshold. Then the log is written to a data store, if the size of the log is greater than the threshold.

Abstract: Described herein are means for implementing consensus on read via a consensus on write smart contract trigger for a Distributed Ledger Technology (DLT) platform in conjunction with a cloud based computing environment.

Abstract: Described herein are systems, apparatus, methods and computer program products configured for actions to be performed on segments within a pipeline. The disclosed systems and techniques allow a user to select a data segment on a graphical user interface. The user may then utilize the data of the segment to perform one or more actions. Thus the data of the segment may be used to provide communications to parties contained within the data, manipulate the data segment based on the parties contained within the data, and change the data displayed based on attributes selected.

Abstract: A message batching configuration may be determined for transmitting a message to recipients. The message batching configuration may include two or more message batches, a respective recipient count for each message batch, a respective time delay between each message batch, and a performance metric for evaluating the message. The message is transmitted in accordance with the message batching configuration. The transmission of subsequent message batches is halted when it is determined that the designated performance metric fails to meet a designated performance metric threshold.

Abstract: A request to perform an action related to a smart contract recorded on a public trust ledger external to the database system may be received via a communication interface at a database system. The request may authenticate a designated database system account. A determination may be made as to whether the designated database system account is authorized to perform the action by accessing definition information for a public trust ledger synthetic party identifying a plurality of database system accounts authorized to perform one or more actions related to the smart contract. The database system may communicate with a token exchange to perform the action by executing the smart contract when it is determined that the designated database system account is authorized to perform the action.