Abstract: A single sign-on is implemented in an online transaction processing system. A security token extracted from a transaction request is received. The security token is validated and, in response to a positive validation, security information is extracted. The security information is processed to validate the transaction request and a set of validation attributes is generated. The set of validation attributes is stored in a read-only data object. A transaction server is notified of the read-only data object to authorize processing of the transaction request by the transaction server.

Abstract: A received security token includes first access control attributes and a signature of a first identity provider of a first security domain. Additional access control attributes provided by a second identity provider of a second security domain are added into the received security token. The received security token with the added additional access control attributes is re-signed, with a private key associated with a certificate of a second service provider in the second security domain. The re-signing is an assertion in the second security domain that the added additional access control attributes have been provided by the second identity provider of the second security domain. The re-signed received security token is issued for consuming, using the added additional access control attributes, by any service provider in the second security domain.

Abstract: A single sign-on is implemented in an online transaction processing system. A security token extracted from a transaction request is received. The security token is validated and, in response to a positive validation, security information is extracted. The security information is processed to validate the transaction request and a set of validation attributes is generated. The set of validation attributes is stored in a read-only data object. A transaction server is notified of the read-only data object to authorize processing of the transaction request by the transaction server.

Abstract: A single sign-on is implemented in an online transaction processing system. A security token extracted from a transaction request is received. The security token is validated and, in response to a positive validation, security information is extracted. The security information is processed to validate the transaction request and a set of validation attributes is generated. The set of validation attributes is stored in a read-only data object. A transaction server is notified of the read-only data object to authorize processing of the transaction request by the transaction server.

Abstract: A received security token includes first access control attributes and a signature of a first identity provider of a first security domain. Additional access control attributes provided by a second identity provider of a second security domain are added into the received security token. The received security token with the added additional access control attributes is re-signed, with a private key associated with a certificate of a second service provider in the second security domain. The re-signing is an assertion in the second security domain that the added additional access control attributes have been provided by the second identity provider of the second security domain. The re-signed received security token is issued for consuming, using the added additional access control attributes, by any service provider in the second security domain.

Abstract: Attribute-based access control is performed across a first and a second security domain in a federated distributed processing environment. A security token received in the second security domain from a first service provider in the first security domain includes access control attributes. Access control information associated with a request to process an online transaction in the second security domain is received from an identity provider in the second security domain. The access control information is mapped into access control attributes compatible with a format of the access control attributes of the received security token. The mapped access control attributes are appended to the received security token to create a modified security token. The modified security token is signed with a certificate of a second service provider in the second security domain, and the modified security token is issued for consuming by any service provider in the second security domain.

Abstract: A legacy machine-oriented language interface definition is received of a new module to be implemented, using an object-oriented language, to provide a new feature within a legacy machine-oriented language application that is executable within a legacy application execution platform. An object-oriented class definition and bridging code that interfaces the object-oriented class definition to the legacy machine-oriented language interface definition are generated. An updated version of the object-oriented class definition is received that includes object-oriented code that implements functionality of the new feature within the new module. A new executable version of the legacy machine-oriented language application is built.

Abstract: A method, system, and computer program product include a processor detecting, ambient noise in the vicinity of the mobile telephone and accessing one or more stored sounds. The processor determines that the ambient noise matches a stored sound of the one or more stored sounds and based on the determining, switches handling of incoming calls to the mobile phone to a predetermined state.

Abstract: A method, system, and computer program product include a processor detecting, ambient noise in the vicinity of the mobile telephone and accessing one or more stored sounds. The processor determines that the ambient noise matches a stored sound of the one or more stored sounds and based on the determining, switches handling of incoming calls to the mobile phone to a predetermined state.

Abstract: Arrangements describe herein relate to updating an e-mail recipient list. A first version of an e-mail can be received, the first version comprising a message header identifying at least a first e-mail recipient. The first version of the e-mail can be sent to the first e-mail recipient indicated in the message header. A second version of the e-mail can be received, the second version of the e-mail indicating at least a second e-mail recipient. The second version can be sent to the at least second e-mail recipient indicated in the message header of the second version. An update request for the first version can be received, the update request configured to be processed to update the message header of the first version to add the at least second e-mail recipient to the message header. The update request can be sent to the at least first e-mail recipient.

Abstract: A single sign-on is implemented in an online transaction processing system. A security token extracted from a transaction request is received. The security token is validated and, in response to a positive validation, security information is extracted. The security information is processed to validate the transaction request and a set of validation attributes is generated. The set of validation attributes is stored in a read-only data object. A transaction server is notified of the read-only data object to authorize processing of the transaction request by the transaction server.

Abstract: Attribute-based access control is performed across a first and a second security domain in a federated distributed processing environment. A security token received in the second security domain from a first service provider in the first security domain includes access control attributes. Access control information associated with a request to process an online transaction in the second security domain is received from an identity provider in the second security domain. The access control information is mapped into access control attributes compatible with a format of the access control attributes of the received security token. The mapped access control attributes are appended to the received security token to create a modified security token. The modified security token is signed with a certificate of a second service provider in the second security domain, and the modified security token is issued for consuming by any service provider in the second security domain.

Abstract: Arrangements describe herein relate to updating an e-mail recipient list. A first version of an e-mail can be received, the first version comprising a message header identifying at least a first e-mail recipient. The first version of the e-mail can be sent to the first e-mail recipient indicated in the message header. A second version of the e-mail can be received, the second version of the e-mail indicating at least a second e-mail recipient. The second version can be sent to the at least second e-mail recipient indicated in the message header of the second version. An update request for the first version can be received, the update request configured to be processed to update the message header of the first version to add the at least second e-mail recipient to the message header. The update request can be sent to the at least first e-mail recipient.

Abstract: Arrangements describe herein relate to updating an e-mail recipient list. A first version of an e-mail can be received, the first version comprising a message header identifying at least a first e-mail recipient. The first version of the e-mail can be sent to the first e-mail recipient indicated in the message header. A second version of the e-mail can be received, the second version of the e-mail indicating at least a second e-mail recipient. The second version can be sent to the at least second e-mail recipient indicated in the message header of the second version. An update request for the first version can be received, the update request configured to be processed to update the message header of the first version to add the at least second e-mail recipient to the message header. The update request can be sent to the at least first e-mail recipient.

Abstract: A legacy machine-oriented language interface definition is received of a new module to be implemented, using an object-oriented language, to provide a new feature within a legacy machine-oriented language application that is executable within a legacy application execution platform. An object-oriented class definition and bridging code that interfaces the object-oriented class definition to the legacy machine-oriented language interface definition are generated. An updated version of the object-oriented class definition is received that includes object-oriented code that implements functionality of the new feature within the new module. A new executable version of the legacy machine-oriented language application is built.

Abstract: A legacy machine-oriented language interface definition of a new module to be implemented within a legacy machine-oriented language application using an object-oriented language is received at a processor. An object-oriented class definition and bridging code that interfaces the object-oriented class definition to the legacy machine-oriented language interface definition is generated by the processor. An updated version of the object-oriented class definition is received that includes object-oriented code that implements functionality of the new module. A new version of the legacy machine-oriented language application is created that includes the new module as a new object accessible using the legacy machine-oriented language interface definition and as implemented by the object-oriented code in the updated version of the object-oriented class definition.

Abstract: Arrangements describe herein relate to updating an e-mail recipient list. A first version of an e-mail can be received, the first version comprising a message header identifying at least a first e-mail recipient. The first version of the e-mail can be sent to the first e-mail recipient indicated in the message header. A second version of the e-mail can be received, the second version of the e-mail indicating at least a second e-mail recipient. The second version can be sent to the at least second e-mail recipient indicated in the message header of the second version. An update request for the first version can be received, the update request configured to be processed to update the message header of the first version to add the at least second e-mail recipient to the message header. The update request can be sent to the at least first e-mail recipient.

Abstract: A legacy machine-oriented language interface definition of a new module to be implemented within a legacy machine-oriented language application using an object-oriented language is received at a processor. An object-oriented class definition and bridging code that interfaces the object-oriented class definition to the legacy machine-oriented language interface definition is generated by the processor. An updated version of the object-oriented class definition is received that includes object-oriented code that implements functionality of the new module. A new version of the legacy machine-oriented language application is created that includes the new module as a new object accessible using the legacy machine-oriented language interface definition and as implemented by the object-oriented code in the updated version of the object-oriented class definition.

Abstract: A method of identifying desired objects of information determines whether an existing rule is appropriate to identify a new desired object of information, defines a new rule to include at least one search query string when one of the existing rules is not appropriate to identify the new desired object of information, and defines an initial new search query string to identify the new desired object of information, wherein the initial search query string has a search query string input value. Furthermore, the method includes identifying objects having an object value equal to the search query string input value, and identifying the objects as the results of the processing operation and as having an equivalence relationship with the initial search query string. When the results do not satisfy the new rule, subsequent search query strings are defined to form a search query string chain.

Abstract: A system for automatically adjusting a music score comprises a display screen and a music scrolling system configured to perform the steps of selecting a music score, the music score being cataloged and stored in a music score database as a first MIDI file, displaying a first portion of the selected music score on the display screen, recording musical notes with a digital device, storing the recorded musical notes in memory as a WAV file, converting the WAV file into a second MIDI file, comparing the first MIDI file and the second MIDI file with a MIDI comparison algorithm, determining if the first MIDI file substantially matches the second MIDI file, automatically adjusting the music score on the display screen upon determining that the first MIDI file substantially matches the second MIDI file, and displaying one or more mistakes upon determining that the first MIDI file does not substantially match the second MIDI file.