Abstract: This disclosure is directed to embodiments of systems and methods for tracking sessions of a user. A session manager executing on a server may establish a plurality of sessions with a web application for a user via a web socket of the session manager. The plurality of sessions may share a first session identifier. The session manager may track, by via a web socket container established for the first session identifier, the plurality of sessions. The session manager may detect a log off by the user from one of the plurality of sessions. The session manager may send a log off event to others of the plurality of sessions tracked via the web socket container, responsive to the detection.

Abstract: This disclosure is directed to embodiments of systems and methods for tracking sessions of a user. A session manager executing on a server may establish a plurality of sessions with a web application for a user via a web socket of the session manager. The plurality of sessions may share a first session identifier. The session manager may track, by via a web socket container established for the first session identifier, the plurality of sessions. The session manager may detect a log off by the user from one of the plurality of sessions. The session manager may send a log off event to others of the plurality of sessions tracked via the web socket container, responsive to the detection.

Abstract: This disclosure is directed to embodiments of systems and methods for tracking sessions of a user. A session manager executing on a server may establish a plurality of sessions with a web application for a user via a web socket of the session manager. The plurality of sessions may share a first session identifier. The session manager may track, by via a web socket container established for the first session identifier, the plurality of sessions. The session manager may detect a log off by the user from one of the plurality of sessions. The session manager may send a log off event to others of the plurality of sessions tracked via the web socket container, responsive to the detection.

Abstract: Described embodiments protect clients from open redirect security vulnerabilities in Web applications. A primary application receives a request for an operation to be performed on behalf of a secondary application. The request includes a return location parameter containing i) a return location, and ii) an encrypted portion. After completing the requested operation, the primary application retrieves the return location parameter and a cryptographic key uniquely associated with the secondary application. The primary application decrypts the encrypted portion of the return location parameter to generate a decrypted value, and uses the decrypted value to validate the return location contained in the return location parameter. The primary application transmits a redirect message to the client that causes the client to be redirected to the return location contained in the return location parameter only in response to the return location being successfully validated based on the decrypted value.

Abstract: This disclosure is directed to embodiments of systems and methods for tracking sessions of a user. A session manager executing on a server may establish a plurality of sessions with a web application for a user via a web socket of the session manager. The plurality of sessions may share a first session identifier. The session manager may track, by via a web socket container established for the first session identifier, the plurality of sessions. The session manager may detect a log off by the user from one of the plurality of sessions. The session manager may send a log off event to others of the plurality of sessions tracked via the web socket container, responsive to the detection.

Abstract: Described embodiments protect clients from open redirect security vulnerabilities in Web applications. A primary application receives a request for an operation to be performed on behalf of a secondary application. The request includes a return location parameter containing i) a return location, and ii) an encrypted portion. After completing the requested operation, the primary application retrieves the return location parameter and a cryptographic key uniquely associated with the secondary application. The primary application decrypts the encrypted portion of the return location parameter to generate a decrypted value, and uses the decrypted value to validate the return location contained in the return location parameter. The primary application transmits a redirect message to the client that causes the client to be redirected to the return location contained in the return location parameter only in response to the return location being successfully validated based on the decrypted value.