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: Embodiments herein describe a pattern or syntax that can be used to convey or express the reason or purpose for a service provider to request user data in an identity federation. A service provider can request user data from the identity provider using an authentication process. If the authentication process is successful, the identity provider provides an authorization token to the service provider which it can use to retrieve the user data. The embodiments herein obtain user consent in the same authentication process used to provide the authorization token. In order to do so, the embodiments herein introduce a pattern or syntax that the service provider uses to convey the purpose for which it wants to use the user data to the identity provider.

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.

Abstract: A personal protective headgear is an apparatus fully enclosing a user's head, protecting not only from potential contamination of breathing air but also from potential physical damage. A facial shield is hermetically sealed around the front-facing portion of the apparatus, preventing entrance of unfiltered air. Fans direct air through a set of filters, thus cleansing air entering the apparatus. The apparatus may further be equipped with a variety of interactivity modules, including cameras, speakers, lights, displays, and more. A set of sensors may be utilized to monitor the user and the user's surroundings in different conditions. The apparatus may also include wireless capabilities that allow the wearer to transfer information to and from a remote user, thereby allowing the user to follow instructions or otherwise interact with a guide or other such remote companion. Swappable battery packs allow the user to avoid losing power, even while replenishing power supplies.

Abstract: Embodiments herein describe a pattern or syntax that can be used to convey or express the reason or purpose for a service provider to request user data in an identity federation. A service provider can request user data from the identity provider using an authentication process. If the authentication process is successful, the identity provider provides an authorization token to the service provider which it can use to retrieve the user data. The embodiments herein obtain user consent in the same authentication process used to provide the authorization token. In order to do so, the embodiments herein introduce a pattern or syntax that the service provider uses to convey the purpose for which it wants to use the user data to the identity provider.

Abstract: An apparatus, system, and method are disclosed for automatically maintaining identity relationships among disparate enterprise information systems. The apparatus comprises a synchronization hub comprising an identity relationship repository, a relationship service module, a consistency module, and an adjustment module. The relationship service is configured to access a target relationship entry using a unique key from a source business object, wherein the source business object is representative of changes made in a source enterprise information system. The various components and modules of the synchronization hub cooperate to determine identity relationships that need updating and to propagate identity relationship changes to one or more destination enterprise information servers.