Welcome Guest Search | Active Topics | Sign In | Register

EO.Web and CitrixReceiver Options
serializer
Posted: Wednesday, February 28, 2018 8:54:15 AM
Rank: Advanced Member
Groups: Member

Joined: 5/9/2016
Posts: 84
Hi,

this page https://payroll.trupay.com/Citrix/XenApp/auth/login.aspx requires that you have installed CitrixReceiver. I did download this from Chrome. It does not add any "add-on" or extension into Chrome but logon works after installing. However, in EO.Web this CitrixReceiver app that needs to be downloaded is not found. You can validate that from the logon page where you can see if it is installed or not.

The question is how I can work with this application needed for logon into EO.Web?
eo_support
Posted: Wednesday, February 28, 2018 9:49:01 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,221
Do you mean EO.Web or EO.WebBrowser? If you meant EO.WebBrowser, then you won't be able to use it because CitrixReceiver is a Chrome App --- As a general rule, everything you need to install through Chrome Web Store won't work because EO.WebBrowser does not include extension/app support.
serializer
Posted: Wednesday, February 28, 2018 9:51:52 AM
Rank: Advanced Member
Groups: Member

Joined: 5/9/2016
Posts: 84
How much work do you think it is to modify EO.WebBrowser to support extensions? I think more and more security solutions require apps and extensions and more and more people are interested in automating this.
eo_support
Posted: Wednesday, February 28, 2018 10:00:57 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,221
I do not believe this is on our priority list now ---- There are many features in Google Chrome that does not exist in EO.WebBrowser, app/extension is just one of them. It is not practical for us to include all of them because of many challenges. Some requires additional UIs, some integrates with Google services, some have license restrictions, etc. Even if we were to work out all those and add everything Chrome has into our product, then you would basically getting Google Chrome. You won't be able to integrate it seamlessly with your application and the distribution would be too large and make a lot of other users who only use the core features as of now very unhappy. So this is a balance that it is not possible to fully satisfy both ends.
serializer
Posted: Wednesday, February 28, 2018 10:16:09 AM
Rank: Advanced Member
Groups: Member

Joined: 5/9/2016
Posts: 84
What about the idea of paying for being able to integrate this? Maybe, I could sponsor this development if the end user helps me with this.
eo_support
Posted: Wednesday, February 28, 2018 10:25:05 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,221
No. It's not something we are exploring at this point and it won't be something you would want either. This is not a few lines of code and Chromium project is an extremely large and constant fast moving project, so something that can cost you 1 day to put in could potentially cost you many days later over and over again as the upstream implementation has been changed/adjusted/improved constantly and you have to keep updating the downstream projects to be in sync. So such one time customization could be extremely costly in the long run.


You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.