Abstract:
Handling access token invalidation is provided. In response to receiving a valid login from a user requesting access to a service, a new access token is issued to the user with a claim containing a container identifier. A first cache corresponding to access tokens issued to the user is searched. In response to identifying a previously issued access token corresponding to the user in the first cache, the previously issued access token is added to a second cache corresponding to stale tokens. The new access token is added to the first cache. In response to receiving the new access token as an identity of the user to access the service, the new access token is validated when the new access token is not identified in the second cache of stale tokens and the container identifier contained in the claim matches an identifier corresponding to a running container of the service.
Abstract:
Arrangements described herein relate to collaborative environments and, more particularly, to use of a microblog to enhance communication in an organization. The present arrangements can include receiving from a first user a first microblog entry into a microblog, identifying at least one keyword associated with the first microblog entry, and assigning to the at least one keyword a tag creating an association between the at least one keyword and at least one data repository. The arrangements further can include establishing bidirectional integration between the microblog and the at least one data repository of information related to the tag creating the association between the at least one keyword and the at least one data repository.
Abstract:
Arrangements described herein relate to collaborative environments and, more particularly, to use of a microblog to enhance communication in an organization. The present arrangements can include receiving from a first user a first microblog entry into a microblog, identifying at least one keyword associated with the first microblog entry, and assigning to the at least one keyword a tag creating an association between the at least one keyword and at least one data repository. The arrangements further can include establishing bidirectional integration between the microblog and the at least one data repository of information related to the tag creating the association between the at least one keyword and the at least one data repository.
Abstract:
An identity provider (IdP) discovery service operative at a service provider (SP) is described. In operation, and as valid requests are received by the SP via normal IdP-initiated flows, the SP builds-up knowledge about the relationship between the IdP (that redirected the request) and the initiator of the request. The IdP instance typically is inferred from an HTTP referrer field, and information about the initiator may be ascertained from client-specific information, such as client system IP address, client DNS domain, a domain of a user e-mail address, a target URL for the incoming request, or the value associated with a particular HTTP header field. This knowledge is maintained in one or more mapping table(s) that associate request attributes-to-IdP instance data. The mappings are then used to facilitate IdP discovery for a new incoming request to the SP that has been determined to originate from other than an IdP.
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:
Handling access token invalidation is provided. In response to receiving a valid login from a user requesting access to a service, a new access token is issued to the user with a claim containing a container identifier. A first cache corresponding to access tokens issued to the user is searched. In response to identifying a previously issued access token corresponding to the user in the first cache, the previously issued access token is added to a second cache corresponding to stale tokens. The new access token is added to the first cache. In response to receiving the new access token as an identity of the user to access the service, the new access token is validated when the new access token is not identified in the second cache of stale tokens and the container identifier contained in the claim matches an identifier corresponding to a running container of the service.
Abstract:
Arrangements described herein relate to collaborative environments and, more particularly, to use of a microblog to enhance communication in an organization. The present arrangements can include receiving from a first user a first microblog entry into a microblog, identifying at least one keyword associated with the first microblog entry, and assigning to the at least one keyword a tag creating an association between the at least one keyword and at least one data repository. The arrangements further can include establishing bidirectional integration between the microblog and the at least one data repository of information related to the tag creating the association between the at least one keyword and the at least one data repository.
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:
Arrangements described herein relate to collaborative environments and, more particularly, to use of a microblog to enhance communication in an organization. The present arrangements can include receiving from a first user a first microblog entry into a microblog, identifying at least one keyword associated with the first microblog entry, and assigning to the at least one keyword a tag creating an association between the at least one keyword and at least one data repository. The arrangements further can include establishing bidirectional integration between the microblog and the at least one data repository of information related to the tag creating the association between the at least one keyword and the at least one data repository.
Abstract:
Arrangements described herein relate to collaborative environments and, more particularly, to use of a microblog to enhance communication in an organization. The present arrangements can include receiving from a first user a first microblog entry into a microblog, identifying at least one keyword associated with the first microblog entry, and assigning to the at least one keyword a tag creating an association between the at least one keyword and at least one data repository. The arrangements further can include establishing bidirectional integration between the microblog and the at least one data repository of information related to the tag creating the association between the at least one keyword and the at least one data repository.