Abstract: A data management system (DMS) may capture snapshots of a computing object in accordance with a service level agreement (SLA). The DMS may store the captured snapshots in a cluster of storage nodes at the DMS and/or transmit the snapshots to one or more external archive locations. Which archive location to store given snapshots of the computing object may be based on archival policies defined in the SLA. Some snapshots may be stored locally at the DMS, some snapshots may be stored in one archive location of a set of multiple candidate archive locations, and some snapshots may be stored in more than one archive location of the set of multiple candidate archive locations. A retention duration for each snapshot may be independent of the archive location for the snapshot. For recovery purposes, a user may specify from which archive location the user selects to retrieve a snapshot.

Abstract: Character input error correction is provided by receiving from a keyboard character input by a user. The character input includes character input errors by the user, the character input errors being input of incorrect characters by the user via the keyboard. The character input errors of the character input are automatically identified and classified into character error classification(s). Each character error classification corresponds to a respective visual transformation of input characters. It is determined that a frequency of the identified and classified character input errors exceeds a predefined threshold confidence level for triggering application of keyboard corrections for user input. Based on the determining, keyboard corrections are applied for user input. The applying keyboard corrections includes applying a correction to character(s) displayed for or input by the user. The applied correction is based on at least one of the classification(s) into which the character input errors are classified.

Abstract: An approach is provided for sharing valid token(s) across application instances. If refresh token rotation is used, (i) a token request is received which includes a number of tokens required, (ii) access and refresh token pairs are generated and shared so that a total number of the pairs equals the number of tokens, and (iii) the access and refresh token pairs are sent to a client so that in response to token requests, the application instances obtain respective access and refresh token pairs. If refresh token rotation is not used, (iv) a request for a refresh token is received, (v) an existing access token is validated, where the access token is bound to the refresh token, and (vi) if the existing access token is expired, a new access token is generated and sent to the client; otherwise, the existing access token is sent to the client.

Abstract: A computer-implemented method for error standardization in a cloud based hybrid application integration environment. The method includes receiving at least one error schema definition for an error type from a software application, and mapping the received at least one error schema definition with a corresponding error schema definition of at least one architecture style. The method includes generating an error mapping object based on the mapping of the received at least one error schema definition and the corresponding error schema definition of the at least one architecture style. The method further includes receiving an error object from the software application, and generating a resolved error object, for the received error object, based on the generated error mapping object.

Abstract: An approach is provided for sharing valid token(s) across application instances. If refresh token rotation is used, (i) a token request is received which includes a number of tokens required, (ii) access and refresh token pairs are generated and shared so that a total number of the pairs equals the number of tokens, and (iii) the access and refresh token pairs are sent to a client so that in response to token requests, the application instances obtain respective access and refresh token pairs. If refresh token rotation is not used, (iv) a request for a refresh token is received, (v) an existing access token is validated, where the access token is bound to the refresh token, and (vi) if the existing access token is expired, a new access token is generated and sent to the client; otherwise, the existing access token is sent to the client.

Abstract: Character input error correction is provided by receiving from a keyboard character input by a user. The character input includes character input errors by the user, the character input errors being input of incorrect characters by the user via the keyboard. The character input errors of the character input are automatically identified and classified into character error classification(s). Each character error classification corresponds to a respective visual transformation of input characters. It is determined that a frequency of the identified and classified character input errors exceeds a predefined threshold confidence level for triggering application of keyboard corrections for user input. Based on the determining, keyboard corrections are applied for user input. The applying keyboard corrections includes applying a correction to character(s) displayed for or input by the user. The applied correction is based on at least one of the classification(s) into which the character input errors are classified.

Abstract: Character input error correction is provided by receiving from a keyboard character input by a user. The character input includes character input errors by the user, the character input errors being input of incorrect characters by the user via the keyboard. The character input errors of the character input are automatically identified and classified into character error classification(s). Each character error classification corresponds to a respective visual transformation of input characters. It is determined that a frequency of the identified and classified character input errors exceeds a predefined threshold confidence level for triggering application of keyboard corrections for user input. Based on the determining, keyboard corrections are applied for user input. The applying keyboard corrections includes applying a correction to character(s) displayed for or input by the user. The applied correction is based on at least one of the classification(s) into which the character input errors are classified.

Abstract: Techniques for generic authentication with arbitrary services are provided. A request to authorize with a first service, of a plurality of services, using the OAuth protocol, is received by a generic client library, from a first application. A set of parameters specific to an implementation of the OAuth protocol provided by the first service are identified in a configuration file. An HTTP request is generated based on the set of parameters identified in the data structure, and the first application is authorized with the first service via the OAuth protocol using the generated HTTP request.

Abstract: Character input error correction is provided by receiving from a keyboard character input by a user. The character input includes character input errors by the user, the character input errors being input of incorrect characters by the user via the keyboard. The character input errors of the character input are automatically identified and classified into character error classification(s). Each character error classification corresponds to a respective visual transformation of input characters. It is determined that a frequency of the identified and classified character input errors exceeds a predefined threshold confidence level for triggering application of keyboard corrections for user input. Based on the determining, keyboard corrections are applied for user input. The applying keyboard corrections includes applying a correction to character(s) displayed for or input by the user. The applied correction is based on at least one of the classification(s) into which the character input errors are classified.

Abstract: A computer-implemented method for error standardization in a cloud based hybrid application integration environment. The method includes receiving at least one error schema definition for an error type from a software application, and mapping the received at least one error schema definition with a corresponding error schema definition of at least one architecture style. The method includes generating an error mapping object based on the mapping of the received at least one error schema definition and the corresponding error schema definition of the at least one architecture style. The method further includes receiving an error object from the software application, and generating a resolved error object, for the received error object, based on the generated error mapping object.

Abstract: An approach is provided for sharing valid token(s) across application instances. If refresh token rotation is used, (i) a token request is received which includes a number of tokens required, (ii) access and refresh token pairs are generated and shared so that a total number of the pairs equals the number of tokens, and (iii) the access and refresh token pairs are sent to a client so that in response to token requests, the application instances obtain respective access and refresh token pairs. If refresh token rotation is not used, (iv) a request for a refresh token is received, (v) an existing access token is validated, where the access token is bound to the refresh token, and (vi) if the existing access token is expired, a new access token is generated and sent to the client; otherwise, the existing access token is sent to the client.

Abstract: An approach is provided for sharing valid token(s) across application instances. If refresh token rotation is used, (i) a token request is received which includes a number of tokens required, (ii) access and refresh token pairs are generated and shared so that a total number of the pairs equals the number of tokens, and (iii) the access and refresh token pairs are sent to a client so that in response to token requests, the application instances obtain respective access and refresh token pairs. If refresh token rotation is not used, (iv) a request for a refresh token is received, (v) an existing access token is validated, where the access token is bound to the refresh token, and (vi) if the existing access token is expired, a new access token is generated and sent to the client; otherwise, the existing access token is sent to the client.

Abstract: Systems, methods, and computer program products to perform an operation comprising receiving, from a first application by a second application, a request to authorize with a first service, of a plurality of services, using the OAuth protocol, identifying, in a data structure by the second application, a set of parameters specific to an implementation of the OAuth protocol provided by the first service, modifying, by the second application, a first parameter of the second application based on the set of parameters identified in the data structure, and authorizing, by the second application, the first application with the first service via the OAuth protocol using the modified first parameter.