Abstract: Mechanisms are provided for salted password protection of computing resources. An entity identifier and password for authenticating an entity to access a protected computing resource are received. A salt value is generated as a random value that is combined with the password to generate a salted password. A hash value is generated based on a hash function and the salted password as an input to the hash function. Based on the password, an encryption key is generated for encrypting the salt value. The salt value is encrypted based on the encryption key and an encryption algorithm to generate an encrypted salt value. The entity identifier, hash value, and encrypted salt value are stored in a secured database for later retrieval to validate subsequent access requests specifying the entity identifier.

Abstract: Mechanisms are provided for salted password protection of computing resources. An entity identifier and password for authenticating an entity to access a protected computing resource are received and a client salt value is generated by a password management engine of a client computing device. A server salt value is generated as a random value that is combined with the client salt value to generate a combined salt value. The combined salt value is combined with the password to generate a combined salted password. A hash value is generated based on a hash function and the combined salted password as an input to the hash function, and the server salt value is encrypted based on an encryption key and an encryption algorithm to generate an encrypted server salt value. The entity identifier, hash value, and encrypted server salt value are stored in a secured database for later validation of access requests.

Abstract: An approach for optimizing security token exchange. The approach receives a first request from a client. The approach extracts a first security token and an API reference. The approach validates the first security token. If the security token is valid, then the approach, calls the API and retrieves a second security token, embeds the second security token in the API and sends a second request with a third security token and the reference to the API to another application in a different domain.