International Business Machines Corporation

Edison Vault, LLC

Globalfoundries Inc.

Gal A Shachor

Todd Eric Kaplinger

Samuel Kallner

Gregory Louis Truty

Artem Spector

Victor S Moore

Thomas Edward Creamer

Pnina A Vortman

Glen R Walters

Haim Schneider

Iddo Levin

Ishai Borovoy

Nili Guy

Yoav Rubin

Idan Ben-Harrush

Anton Aleksandrov

Andrew Dwight Dingsor

Michael R Rheinheimer

Nataraj Nagaratnam

Sudheesh S Kairali

Sreekanth Ramakrishna Iyer

Vijay R Kalangumvathakkal

Alexey Roytman

Karunakar Bojjireddy

Issahar Weiss

Uri Zonens

Alexander Dvinsky

Cirill Aizenberg

Vitaly Meytin

Arie Shifer

Omer Tripp

Ben Z Akselrod

Francisco Phelan Curbera

Segev Eliezer Wasserkrug

Michael L Fraenkel

Nitzan Nissim

Avi Yaeli

Konstantin Shagin

Asaf Adi

Matthew Jason Duftler

Rania Yousef Khalaf

Axel Martens

Dmitri Pikus

Uri Shani

Michael C Mansell

Amit Fisher

David Franklin Manning

Ariel Landau

Dagan Gilat

Andrei Kirshin

David Oren

Alex Melament

Maya Barnea

Tirtsa Hochberg

Bruno Wasserman

Moty Drimer

Anat Berkman

Johannes Riemer

Eishy Smith

Ran Bernstein

Nili Guy Ifergan

Gilad Moredehi Saadoun

A method, system and computer program product for integrating a mobile payment application with other mobile applications while preventing security exposures. A set of application programming interfaces of mobile applications that may possibly be utilized by a pass created by a mobile payment application is generated in response to receiving an indication that the pass was created. A 'pass,' as used herein, refers to a form of mobile payment, such as a gift card. A selection of these application programming interfaces may then be received to interact with the created pass. In this manner, the existing mobile applications are seamlessly integrated with the features of passes. Furthermore, a virtual container is created for the created pass and the selected application programming interfaces to interface with the created pass. By creating such a container, the data to be exposed to the application layer can be controlled.

Integrating mobile payment application with other mobile applications while preventing security exposures

An approach to secure API access for distinct types of users. A request for access to an API from a user is initiated and followed by sending a request for a login credential to the user based on a type of API requested: Data API or Interaction API. The login credential is received along with the network location of the user. Authenticating the login credential and create an API specific token. Assigning the API specific token to a user activity and granting the user access to the specific API.

User profile access from engaging applications with privacy assurance associated with an API

A computer-implemented method for distributing digital certificates. A request for a digital certificate is received from a requesting system. A deployment challenge is sent to the trust agent running on the requesting system. A response to the deployment challenge is received from the trust agent running on the requesting system. The response to the deployment challenge is evaluated to determine whether the response is correct. The digital certificate is distributed to the requesting system in response to a determination that the response to the deployment challenge is correct.

Secure trust based distribution of digital certificates

A system and non-transitory computer program product for distributing digital certificates. A request for a digital certificate is received from a requesting system. A deployment challenge is sent to the trust agent running on the requesting system. A response to the deployment challenge is received from the trust agent running on the requesting system. The response to the deployment challenge is evaluated to determine whether the response is correct. The digital certificate is distributed to the requesting system in response to a determination that the response to the deployment challenge is correct.

Integrated mobile payment application with other mobile applications while preventing security exposures

Examples of techniques for authenticating mobile applications are described herein. A method includes receiving, via a first server, a key pair and a policy file associated with a mobile service from a second server. Authentication of the mobile application is performed based on the key pair and the policy file. A scope token is generated with an application scope in response to authenticating the mobile application. Authentication of a client device is performed corresponding to the mobile application and a user to generate a doubly-authenticated scope token including a device scope and application authenticity scope. The doubly-authenticated scope token is sent to a security gateway for user authentication. A trebly-authenticated scope token is received with a grant token request and a grant token is sent to the mobile application. The grant token is received from the mobile application. An access token is generated and sent to the mobile application.

Authenticating mobile applications using policy files

Examples of techniques for authenticating mobile applications are described herein. A method can include receiving, by a processor, a key pair and a policy file associated with a mobile service. The processor can receive a service request from a mobile application at a security gateway. The processor can detect that the service request includes an invalid or missing access token. The processor can redirect the mobile application to request a grant token from an authorization end point on a server. The processor can receive a grant token request from the mobile application and forward the grant token request to the server based on a policy file, the policy file including a list of: a plurality of security objects to be authenticated, a plurality of computing devices to authenticate the security objects, and an order of authentication.

Managing data access on a computing device by receiving at a first computing device first webpage-related content received from a second computing device via a communications network, storing the first webpage-related content in a locally-accessible data storage medium that is locally accessible to the first computing device, causing an agent executed by the first computing device to access the first webpage-related content from the locally-accessible data storage medium, intercepting an attempt by the agent to receive second webpage-related content via the communications network, and providing the second webpage-related content to the agent from the locally-accessible data storage medium.

Managing data access on a computing device

According to an aspect, techniques for processing hybrid data include receiving a web request and translating the web request into a translated native request. The translated native request and a native request are sent to a server via a single web client. A response is received from the server via the single web client. It is determined whether the response corresponds to the translated native request or to the native request.

Processing hybrid data using a single web client

Examples of techniques for authenticating mobile applications are described herein. A method includes receiving, at a first server, a key pair and a policy file associated with a mobile service on a second server, the policy file includes a plurality of security objects to be authenticated, a plurality of computing devices to authenticate the security objects, and an order of authentication. The method includes distributing the key pair and the policy file to a security device. The method also includes receiving, at the first server, an authentication request from a mobile application. The method further includes creating an authenticity challenge as specified in the policy file and sending the authenticity challenge with a response to the mobile application.

Growing community of inventors

Yokneam, Israel

Gal A Shachor