Abstract: Embodiments present different password-less sign-in alternatives for selection by the user for a subsequent future login to the service provider account interface, and in response to determining that data inputs from a user satisfy associated data requests, enable the selected password-less sign-in alternative for a subsequent login of the user into the service provider account interface, wherein the subsequent login of the user into service provider account interface via the enabled selected password-less sign-in alternative does not require the user to enter the password.

Abstract: Aspects refresh permission credentials by populating within user profile data sets cached for members an invalidated value and a first timestamp of said populating the invalidated value; selecting user profile data sets including the invalidated value; identifying a second timestamp of time of creation of the permission credential within the selected user profile data sets; and in response to determining that a time elapsed between the first and second timestamps does not exceed a threshold, rebuilding the selected user profile data sets to include an updated value of the permission credential and set the second timestamp value to a current time of the rebuild, and cache (store) the rebuilt selected user profile data set within the repository.

Abstract: Aspects store configuration version data for an application into a shared cache in a structured data format; in response to a request at run-time for the configuration version data, determine whether run-time format data of the configuration version data is stored in a different, local cache; and in response to determining that the run-time format configuration version data is not stored in the local cache, during execution of the application, read the structured data format data from the shared cache, translate the read data into the run-time data format, store the translated data into the local cache in the run-time format file and return the configuration version run-time format data stored within the local cache in satisfaction of the request at run-time for the configuration version data of the application.

Abstract: In response to determining that an application programming interface call made in response to a first request for the call has failed and that no fail entry has been set for the call, aspects increment a fail count value and set a fail entry for the call that includes a fail response generated by the failure of the call; in response to determining that the call has failed in response to a subsequent, second request for the call, determine whether the incremented fail count value meets a limit value, and if so, set a paused timestamp value for the fail entry; and in response to additional requests for the call occurring within a pause period of time from the paused timestamp value, pause making the call and return the fail entry set for the call in satisfaction of said additional requests.

Abstract: In response to determining that an application programming interface call made in response to a first request for the call has failed and that no fail entry has been set for the call, aspects increment a fail count value and set a fail entry for the call that includes a fail response generated by the failure of the call; in response to determining that the call has failed in response to a subsequent, second request for the call, determine whether the incremented fail count value meets a limit value, and if so, set a paused timestamp value for the fail entry; and in response to additional requests for the call occurring within a pause period of time from the paused timestamp value, pause making the call and return the fail entry set for the call in satisfaction of said additional requests.

Abstract: Aspects store configuration version data for an application into a shared cache in a structured data format; in response to a request at run-time for the configuration version data, determine whether run-time format data of the configuration version data is stored in a different, local cache; and in response to determining that the run-time format configuration version data is not stored in the local cache, during execution of the application, read the structured data format data from the shared cache, translate the read data into the run-time data format, store the translated data into the local cache in the run-time format file and return the configuration version run-time format data stored within the local cache in satisfaction of the request at run-time for the configuration version data of the application.

Abstract: Aspects refresh permission credentials by populating within user profile data sets cached for members an invalidated value and a first timestamp of said populating the invalidated value; selecting user profile data sets including the invalidated value; identifying a second timestamp of time of creation of the permission credential within the selected user profile data sets; and in response to determining that a time elapsed between the first and second timestamps does not exceed a threshold, rebuilding the selected user profile data sets to include an updated value of the permission credential and set the second timestamp value to a current time of the rebuild, and cache (store) the rebuilt selected user profile data set within the repository.