International Business Machines Corporation

Jared R Page

Luke Biddle

Russell A Currey

Sam Lewis

Shane Bradley Weeden

Dale Bowie

Leo M M Farrell

Jasmine Anne Smith

A method, system, and computer program product for frictionless mutual authentication of unsolicited communications may detect an incoming communication. A verification interface may be displayed on a consumer device. On the consumer device, a first valid verification may be received via the verification interface. In response to receiving the first valid verification, a challenge interface may be presented to an enterprise device. On the enterprise device, a second valid verification may be received via the challenge interface. In response to receiving the second valid verification, a verification credential may be presented to both the consumer device and the enterprise device. A connection for the incoming communication may be established between the consumer device and the enterprise device.

Mutual identity verification

In response to detecting a code change request for a particular file of multiple files of a software build during testing, a computer generates a sensitivity rating of the particular file to cause breaks in the software build based on a relative level of failure of the particular file as compared to the multiple files based on one or more factors. The computer outputs a response to the code change request based on the sensitivity rating to one or more integrated development environment interfaces with access to the particular file of the software build. The computer uses the sensitivity rating to determine whether to grant the code change request.

Monitoring code sensitivity to cause software build breaks during software project development

A credential associated with a username is received from a user. The credential is verified. A key identification and a first one-time password are received from a hardware token device. In response to validating the first one-time password, the username is linked to the key identification. A first access token and a first refresh token are generated. The first access token and the first refresh token are sent to the user.

Second factor authorization via a hardware token device

A selection of one or more files for a project plan for a software build is identified. A historical assessment of one or more developers available during a build timeline for the project plan is accessed, the historical assessment comprising an assessment value calculated from one or more previously evaluated sensitivity ratings from one or more previously edited files by the one or more developers of one or more previous software builds. An optimized selection of the one or more developers is assigned to each selection of one or more files based on the historical assessment. The optimized selection of the one or more developers for each selection of one or more files in the project plan for the software build is output.

Developing software project plans based on developer sensitivity ratings detected from monitoring developer error patterns

In response to detecting a software build break during testing, a change to a particular file committed to the software build that caused the software build to break is identified. A record of the change to the particular file is added to a sensitivity database, the sensitivity database accumulating multiple records of changes to the files of the software build during development of the software build. A relative level of failure of the particular file from the files of the software build based on the record in comparison with the multiple records is calculated. A sensitivity rating of the particular file to cause breaks in the software build based on the relative level of failure of the particular file weighted by one or more factors is generated. The sensitivity rating is output to one or more integrated development environment interfaces with access to the particular file of the software build.

Growing community of inventors

Queensland, Australia

Jared R Page