Abstract: Techniques are provided for using tokenization in conjunction with “behind-the-wall” JWT authentication. “Behind-the-wall” JWT authentication refers to JWT authentication techniques in which the JWT stays exclusively within the private network that is controlled by the web application provider. Because the JWT stays within the private network, the security risk posed by posting the JWT in a client cookie is avoided. However, because JWT is used behind-the-wall to authenticate a user with the services requested by the user, the authentication-related overhead is significantly reduced.

Abstract: Techniques are provided for using tokenization in conjunction with “behind-the-wall” JWT authentication. “Behind-the-wall” JWT authentication refers to JWT authentication techniques in which the JWT stays exclusively within the private network that is controlled by the web application provider. Because the JWT stays within the private network, the security risk posed by posting the JWT in a client cookie is avoided. However, because JWT is used behind-the-wall to authenticate a user with the services requested by the user, the authentication-related overhead is significantly reduced.

Abstract: Techniques are provided for using tokenization in conjunction with “behind-the-wall” JWT authentication. “Behind-the-wall” JWT authentication refers to JWT authentication techniques in which the JWT stays exclusively within the private network that is controlled by the web application provider. Because the JWT stays within the private network, the security risk posed by posting the JWT in a client cookie is avoided. However, because JWT is used behind-the-wall to authenticate a user with the services requested by the user, the authentication-related overhead is significantly reduced.

Abstract: A bulk-selection control is described in which the same user input action automatically causes both (a) scrolling of a list of visual indicators of items, and (b) selection of the items that correspond to the visual indicators. Specifically, as the visual indicator of an item is scrolled beyond a “selection-triggering position”, the visual indicator is visually marked to indicate that the corresponding item is selected, and the corresponding item is automatically added to a set of selected items. When scrolled the opposite direction, the items that have already been added to the set of selected items are not removed therefrom, even if the scrolling operation causes their visual indicators to cease to be beyond the selection-triggering position.

Abstract: A bulk-selection control is described in which the same user input action automatically causes both (a) scrolling of a list of visual indicators of items, and (b) selection of the items that correspond to the visual indicators. Specifically, as the visual indicator of an item is scrolled beyond a “selection-triggering position”, the visual indicator is visually marked to indicate that the corresponding item is selected, and the corresponding item is automatically added to a set of selected items. When scrolled the opposite direction, the items that have already been added to the set of selected items are not removed therefrom, even if the scrolling operation causes their visual indicators to cease to be beyond the selection-triggering position.

Abstract: Techniques are provided for using tokenization in conjunction with “behind-the-wall” JWT authentication. “Behind-the-wall” JWT authentication refers to JWT authentication techniques in which the JWT stays exclusively within the private network that is controlled by the web application provider. Because the JWT stays within the private network, the security risk posed by posting the JWT in a client cookie is avoided. However, because JWT is used behind-the-wall to authenticate a user with the services requested by the user, the authentication-related overhead is significantly reduced.

Abstract: Techniques a provided for performing multi-system operations in which changes are asynchronously committed in multiple systems. Metadata about the multi-system operation is injected into the commit logs of one system involved in a multi-system operation. An event stream is generated based on the commit logs of the one system, and is used to drive the operations that one or more other systems need to perform as part of the multi-system operation. A reconciliation system reads the logs of all systems involved in the multi-system operation and determines whether the multi-system operation completed successfully. Techniques are also provided for using machine learning to generate models of normal execution of different types of operations, detect anomalies, pre-emptively send expectation messages, and automatically suggest and/or apply fixes.