The user works in an ASP.NET application in a browser, the results of work on the server are saved by the WCF service, implemented in the same application. At this moment, the client program is running on the computer user, which can request the obtained results of the user's work from this WCF service to save them on the user's computer.
There is one unsolved problem, there is no user identification : if while user А
working on his browser, user B
starts the client program, he can download data from user B
At the moment, it works for me.
It is necessary to somehow identify the client programs, including when the user on the browser works as anonymous (not logged in). There is an idea to use the id of the current session HttpContext.Current.Session.SessionID
. But how does this value transfer to the client program?
For the user, everything should happen in the background, only requests for confirmation of the operation (eg from the browser) are allowed.
Who has any thoughts?
SessionId
file, the client program reads. 2. At the beginning of the session, launch a copy of the client program (store the location in cookies) with theSessionId
parameter. You can run withJS
orCOM
(IE only). - Ildarон сможет скачать данные пользователя A
? - tCode