Abstract: Systems and methods are provided that automatically process a message input, construct an intelligent query based on the processing of the message input, and provide at least one attachable entity according to the processing results and the intelligent query. In some example aspects, a message is received. A natural language processor to determine if the message is requesting content may then process the message. If the message is determined to be requesting content, then candidate sub-queries may be generated to serve as a training set for a query that will be sent to an external search engine to retrieve the attachable entity. The sub-queries may be ranked in order of relevance and performance score. The highest ranked sub-queries may then be used in the actual query that is fired against the external search engine. The external search engine may search local and remote repositories for the top K most relevant attachable entities and present them to a user for attachment in a reply message.

Abstract: Systems and methods are provided that automatically process a message input, construct an intelligent query based on the processing of the message input, and provide at least one attachable entity according to the processing results and the intelligent query. In some example aspects, a message is received. A natural language processor to determine if the message is requesting content may then process the message. If the message is determined to be requesting content, then candidate sub-queries may be generated to serve as a training set for a query that will be sent to an external search engine to retrieve the attachable entity. The sub-queries may be ranked in order of relevance and performance score. The highest ranked sub-queries may then be used in the actual query that is fired against the external search engine. The external search engine may search local and remote repositories for the top K most relevant attachable entities and present them to a user for attachment in a reply message.

Abstract: A client is authenticated by a server receiving an initial request from the client at the beginning of a session. The server receiving the initial request generates an authentication token and returns the authentication token to the client in response to the client being authenticated. The user's credentials used to authenticate the client are stored in the authentication token along with other information. After receiving the authentication token from the server that generated the authentication token, the client passes the authentication token with each of the future requests to the pool of servers. Using the client to pass the transferrable authentication token, the servers share the user's identity/credentials in a decentralized manner. Any server from the shared pool of servers that receives a subsequent client request is able to decrypt the token and re-authenticate the user without having to prompt the client for authentication credentials again.

Abstract: A client is authenticated by a server receiving an initial request from the client at the beginning of a session. The server receiving the initial request generates an authentication token and returns the authentication token to the client in response to the client being authenticated. The user's credentials used to authenticate the client are stored in the authentication token along with other information. After receiving the authentication token from the server that generated the authentication token, the client passes the authentication token with each of the future requests to the pool of servers. Using the client to pass the transferrable authentication token, the servers share the user's identity/credentials in a decentralized manner. Any server from the shared pool of servers that receives a subsequent client request is able to decrypt the token and re-authenticate the user without having to prompt the client for authentication credentials again.