Partner app: JET.navigate({name:"Eikon Explorer App", url:"http://www.google.com", target:"replac...

Zhenya Kovalyov

...e"})

A partner can't use

JET.navigate({name:"Eikon Explorer App", url:"http://www.google.com", target:"replace"})

It looks like that the reason for this is that the external url is opened in the "Internet Explorer Object" by default, and since "Eikon Explorer App" and "Internet Explorer Object" are of different types, one can't "replace" another.

The client's intention is the following:

1. Initialize JET
2. Read a user email from JET.getUserInfo()
3. Redirect a user to the client specified url, passing this user's email as a param
4. Perform automatic login

Do we allow this type of JET usage? What could I recommend?

nkolba

The web renderer for Eikon (where JET is enabled) is only used for whitelisted domains that are either part of Eikon - or an Open Eikon App in the Eikon Library, all other urls will be shunted to the Internet Explorer Object. This behavior is critical to the security model of Eikon.

What is the external url that is being redirected to? Is there anything driving the automatic login besides t email address? If they just need to key off the email, they could could just pass this on the query string to the site they are redirecting to.