Hi,

We currently have ScreenConnect installed on one of our servers and are using it to provide service to our clients. However, the current setup forces us to forward all of our clients to that specific server, and to host/guest pages that really aren’t part of our site.

I am currently trying to integrate ScreenConnect 2.3 into our site, and was hoping to get some feedback and help. Looking through the page code, it seemed like everything relied on Service.ashx, and the pages would make ajax calls to the service methods. So we were thinking that we could install ScreenConnect on an app server, and have our website code make the ajax calls to that server directly (eliminating the need to forward customers to the host/guest pages).

However, so far, I have failed to make this work. The ajax call from the client side is being made without error, but nothing on the server side seems to be happening. My suspicion is that I am failing a security check. If that is the case, what would be the best way to handle that. I would really appreciate any help/advice you can offer.

I would also be interested in any other suggestions on how we should integrate ScreenConnect with our site. I understand you have an iframe option, but given the amount of customization we have done, and would like to do to ScreenConnect, we feel that an iframe is not the best solution.

Thanks

yes i have debugged on the browser side, and i am not getting any errors, and the invokeService method (createSession in this case) is returning a Sys.Net.WebRequest object. The call is hitting Service.ashx, but nothing is happening. The reason i suspect it is a security issue is that the _resultObject of the return object's _executor property is null. If i am on the ScreenConnect Host page and am signed in, it is not null, but if i was logged out, _resultObject is null. So maybe i need to have a method that authenticates the user, before executing other service methods?

Obviously i can't be sure that it is a security issue since i can't step through the Service.ashx code, but that is my guess. Any help on this issue would be much appreciated

i know that it is asynchronus, what i'm saying is i'm not getting anything back at all. I would do 2 exactly identical javascript calls in the console, one on my site page, one on the host page. both ajax calls are made to the url "http://xxx/Service.ashx", one will succeed and the other will get absolutely nothing.

Another difference i have found in the 2 results is, one's _responseAvailable is false, and the other's is true

My apologies, I failed to realize that I was running into the same origin policy.

I am currently looking into cross origin resource sharing, would you happen to have any tips on how to implement it in the ScreenConnect code/configs?

The backup solution would be to use a reverse proxy, but i would very much like to avoid that if possible

Thank you Jake, that worked perfectly. I believe i really only have 1 problem/question left:

What would be the best way to handle/bypass the user authentication. We have users log in at our site already, so we would really like to avoid users from needing to log in twice.

I guess I would need to write a log in method? What would that method look like?

Here is a login method for forms authentication you can put in your service.ashx:

How does your auth work? What's the backend? Will the user have a cookie? Or what if not a cookie?

Regardless of what it is, you should be fine. But get ready to write some C#. You'll likely need to provide an implementation for an ASP.NET RoleProvider and MembershipProvider.

Try creating a System.Web.IHttpModule called CustomAuthenticationModule that subscribes to the AuthenticateRequest event. In your handler you need to set the HttpContext.Current.User principal, probably to a GenericPrincipal with the username and roles they have in your system.

Implement a role provider CustomRoleProvider deriving from Elsinore.ScreenConnect.ReadOnlyRoleProvider. Just override the GetRolesForUser method. This method will be called with the value from HttpContext.Current.User.Identity.Name that you should have populated from your module.

I guess you'll want to change this:



to this:



Put the cs files for both your http module and your role provider in a directory called App_Code off your install root.

Your role manager section should probably look like this:



Your httpModules section should add your module:

Same here, haven't had much luck. Any examples would be appreciated.