Ropes & Gray @ Gemalto Complaint with PUSH NOTIFIC
Post# of 82672
Quote:
When a user wants to access a protected application, the user’s request is redirected to SAS, which sends a push notification out-of-band to the user’s mobile device requesting authorization.
Quote:
When the push notification arrives on the user’s mobile device , the user can respond to the request directly on the push notification , or tap on the notification to load additional request details within the MobilePASS+ application and/or tap to approve the login request, or log in using a fingerprint sensor.
Quote:
Gemalto provides documentation and instructions for integrating Push OTP with thirdparty applications including, but not limited to, applications provided by Blue Coat, Check Point, Cisco, Citrix, F5, Pulse Secure, and SonicWall. See, e.g., Exhibit G at 11.
Quote:
The Infringing Products receive at a security computer in a second channel (e.g., SAS or Ezio server) the demand for access and the login identification and output a prompt requesting transmission of data (e.g., push notification to user’s mobile device requesting user to confirm or deny authorization ). See, e.g., Exhibit F at 1.
Quote:
The Infringing Products include, in an authentication channel,
a prompt mechanism for instructing said accessor to enter predetermined data at and transmit said predetermined data from said peripheral device (e.g., an element of the system that issues a push notification on the user’s mobile device prompting the user to confirm or deny authorization )